OS4X check running daemons - Revision history

Admin: /* checking OS4X client daemon */

2025-09-17T15:03:54Z

checking OS4X client daemon

2025-09-11T11:39:13Z

PID files

2025-09-11T11:38:49Z

checking OS4X receive daemon

2025-09-11T11:38:22Z

Which processes must run

2025-09-11T11:36:06Z

checking OS4X client daemon

2024-10-10T14:23:30Z

Which processes must run

2017-03-09T15:47:12Z

normal situation

2011-07-15T07:35:45Z

2011-07-15T07:35:34Z

2011-07-15T07:29:53Z

@@ Line 96: / Line 96: @@
 <pre>
 os4xbox:~# lsof -p 4979 | grep LISTEN
-os4xdebug 4979 www-data    3u  IPv4 84639858             TCP localhost:60000 (LISTEN)
+os4xdebug 4979 www-data    3u  IPv4 84639858             TCP localhost:10002 (LISTEN)
 </pre>

@@ Line 39: / Line 39: @@
 -rw-rw-rw- 1 www-data www-data 5 Mar  9 14:32 /opt/os4x/tmp/os4xrd.pid
 -rw-rw-rw- 1 www-data www-data 5 Mar  9 14:32 /opt/os4x/tmp/os4xsqd.pid
 root@os4xvirtual:~# cat /opt/os4x/tmp/os4xclientd.pid
 root@os4xvirtual:~#

@@ Line 50: / Line 50: @@
 www-data  3772  3771  0 08:58 ?        00:00:00 os4xrd_tcpip
 www-data  3773  3771  0 08:58 ?        00:00:00 os4xrd_tcpip_tls
 </pre>
 Process IDs explained:
@@ Line 56: / Line 55: @@
 *3772: daemon listening on port 3305
 *3773: daemon listening on port 6619
 When checking the open ports, the tool "<code>lsof</code>" is very handy:

@@ Line 4: / Line 4: @@
 **<code>os4xrd_tcpip</code>: The OS4X receive daemon for accepting TCP/IP connections
 **<code>os4xrd_tcpip_tls</code>: The OS4X receive daemon for accepting TLS secured TCP/IP connections for OFTP2
 *<code>os4xsqd</code>: OS4X send queue daemon. Parent process of running actions started by this process, like sending send queue entries, polling partners, updating CRLs etc.

@@ Line 100: / Line 100: @@
 os4xbox:~# lsof -p 4979 | grep LISTEN
 os4xdebug 4979 www-data    3u  IPv4 84639858             TCP localhost:60000 (LISTEN)
 </pre>

@@ Line 7: / Line 7: @@
 **(<code>os4xrd_capi_x</code>: subsequent ISDN controller receivig processes, if more controllers are configured)
 *<code>os4xsqd</code>: OS4X send queue daemon. Parent process of running actions started by this process, like sending send queue entries, polling partners, updating CRLs etc.
 In case you have OS4X Enterprise, the following process must also exist:
 *<code>os4xclientd</code>: OS4X client daemon, responsible for user authentification and OS4X Enterprise job processing
 == How do the processes save their state ==

@@ Line 26: / Line 26: @@
 === normal situation ===
 In a running envirnonment, a normal situation can be checked manually with the following command. In case of problems please refer to your operating system manual or system administrator.
 ==== checking OS4X receive daemon ====

@@ Line 123: / Line 123: @@
 === Starting daemon forced via web interface ===
 The web interface offers an easy way to start the processes in forced way: just click on the "<code>start forced</code>" link. A popup asks you if you are really sure about this situation, which you must accept with "OK" in order to start forced:
 [[Image:StartForcedQuestion.png]]

← Older revision		Revision as of 07:35, 15 July 2011
Line 99:		Line 99:

	== When to start in 'forced' mode? ==		== When to start in 'forced' mode? ==
		+	If the critical situation is identifed, and you're absolutely sure that the processes really are not running, you can start them forced.
		+	=== Starting daemons forced on commandline ===
		+	When trying to start normally, an error shows the situation:
		+	<pre>
		+	os4xbox:~# /opt/os4x/bin/os4xrd
		+	ERROR: There seems to run another os4xrd2 with pid 3771!
		+	Either you stop it or you clean up the database.
		+	Database name: 'os4x'
		+	SQL statement needed for cleanup:
		+	UPDATE `os4x_pids` SET `pid`='-1' WHERE `program`='os4xrd' AND `serverID`=0
		+	alternatively, start program with parameter '-f':
		+	/opt/os4x/bin/os4xrd -f
		+	</pre>
		+
		+	All daemons understand the optional start parameter "<code>-f</code>" for a forced start:
		+	<pre>
		+	os4xbox:~# /opt/os4x/bin/os4xrd -f
		+	os4xbox:~# /opt/os4x/bin/os4xsqd -f
		+	os4xbox:~# /opt/os4x/bin/os4xclientd -f
		+	os4xbox:~# /opt/os4x/bin/os4xdebugd -f
		+	</pre>
		+
		+	=== Starting daemon forced via web interface ===
		+	The web interface offers an easy way to start the processes in forced way: just click on the "<code>start forced</code>" link. A popup asks you if you are really sure about this situation, which you must accept with "OK" in order to start forced:
		+	[[Image:StartForcedQuestion.png]]

@@ Line 88: / Line 88: @@
 In this example, the OS4X administrative web interface shows that the daemons should be running with the following PIDs:
 [[Image:PIDList.png]]
 But processes don't exist:
 <pre>