Seon check running daemons - Revision history

Admin at 07:35, 15 July 2011

2011-07-15T07:35:45Z

Admin at 07:35, 15 July 2011

2011-07-15T07:35:34Z

Admin at 07:29, 15 July 2011

2011-07-15T07:29:53Z

Admin at 07:29, 15 July 2011

2011-07-15T07:29:36Z

Admin at 07:26, 15 July 2011

2011-07-15T07:26:05Z

Admin at 07:22, 15 July 2011

2011-07-15T07:22:29Z

Admin at 07:16, 15 July 2011

2011-07-15T07:16:15Z

Admin at 07:16, 15 July 2011

2011-07-15T07:16:00Z

Admin at 07:15, 15 July 2011

2011-07-15T07:15:44Z

Admin: New page: == Which processes must run == In order to keep Seon running, the following processes must exist: *`seonrd`: The Seon master receive daemon (parent process of the subsequent rec...

2011-07-15T07:06:23Z

New page: == Which processes must run == In order to keep Seon running, the following processes must exist: *<code>seonrd</code>: The Seon master receive daemon (parent process of the subsequent rec...

New page

== Which processes must run ==
In order to keep Seon running, the following processes must exist:
*<code>seonrd</code>: The Seon master receive daemon (parent process of the subsequent receive daemon processes)
**<code>seonrd_tcpip</code>: The Seon receive daemon for accepting TCP/IP connections
**<code>seonrd_tcpip_tls</code>: The Seon receive daemon for accepting TLS secured TCP/IP connections for OFTP2
**<code>seonrd_capi_0</code>: The Seon receive daemon for accepting ISDN connections on the first ISDN controller
**(<code>seonrd_capi_x</code>: subsequent ISDN controller receivig processes, if more controllers are configured)
*<code>seonsqd</code>: Seon send queue daemon. Parent process of running actions started by this process, like sending send queue entries, polling partners, updating CRLs etc.
*<code>seondebugd</code>: Seon debug daemon which collects debugging information from every Seon process for problem reporting

In case you have Seon Enterprise, the following process must also exist:
*<code>seonclientd</code>: Seon client daemon, responsible for user authentification and Seon Enterprise job processing

== How do the processes save their state ==
Every Seon daemon process saves its PID (process ID) in the database. If a value exists in the database on startup, the daemon refuses to start with the message that another daemon must be running at the moment. In some rare cases, the database information may not meet the real situation, when PIDs are saved in the database and no processes are running. In this case, you can start the daemon in 'forced' mode which overrides the PID check at daemon start.

'''<u>Beware:</u>''' If more than one daemon is running, racing conditions occur between the different running programs, mostly leading to problems in receiving or sending files. This situation is highly unsupported and absolutely to be avoided!

== Identify running processes ==

== When to start in 'forced' mode? ==

@@ 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>
		+	seonbox:~# /opt/seon/bin/seonrd
		+	ERROR: There seems to run another seonrd2 with pid 3771!
		+	Either you stop it or you clean up the database.
		+	Database name: 'seon'
		+	SQL statement needed for cleanup:
		+	UPDATE `seon_pids` SET `pid`='-1' WHERE `program`='seonrd' AND `serverID`=0
		+	alternatively, start program with parameter '-f':
		+	/opt/seon/bin/seonrd -f
		+	</pre>
		+
		+	All daemons understand the optional start parameter "<code>-f</code>" for a forced start:
		+	<pre>
		+	seonbox:~# /opt/seon/bin/seonrd -f
		+	seonbox:~# /opt/seon/bin/seonsqd -f
		+	seonbox:~# /opt/seon/bin/seonclientd -f
		+	seonbox:~# /opt/seon/bin/seondebugd -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 Seon administrative web interface shows that the daemons should be running with the following PIDs:
 [[Image:PIDList.png]]
 But processes don't exist:
 <pre>

← Older revision		Revision as of 07:29, 15 July 2011
Line 87:		Line 87:
	A critical situation is, when PIDs are saved in the database and no corresponding Seon process exists.		A critical situation is, when PIDs are saved in the database and no corresponding Seon process exists.

		+	In this example, the Seon administrative web interface shows that the daemons should be running with the following PIDs:
		+	[[Image:PIDList.png]]
		+	But processes don't exist:
		+	<pre>
		+	seonbox:~# ps -ef \|grep 3772 \| grep -v grep
		+	seonbox:~#
		+	</pre>
		+	Since no process is running, this is a stale situation.

	== When to start in 'forced' mode? ==		== When to start in 'forced' mode? ==

@@ Line 71: / Line 71: @@
 seonbox:~# lsof -p 4724 | grep LISTEN
 seondebug 4724 www-data    3u  IPv4 84970858             TCP localhost:10001 (LISTEN)
 </pre>
 === critical situation ===
 == When to start in 'forced' mode? ==

@@ Line 21: / Line 21: @@
 ''All examples are being shown in a Linux environment. If you have another supported Unix environment (like AIX, HP/UX or Solaris) you may need to modify the command accordingly.''
 === normal situation ===
 The process table will be checked for running "<code>seonrd</code>" processes:
 <pre>
@@ Line 48: / Line 53: @@
 Checking ISDN incoming call acceptance is a little bit more complicated, which is described elsewhere.
 === critical situation ===

@@ Line 41: / Line 41: @@
 seonbox:~# lsof -p 3772 | grep LISTEN
 seonrd  3772 www-data    3u  IPv4 84960962             TCP *:3305 (LISTEN)
-<pre>
+</pre>
 <pre>
 seonbox:~# lsof -p 3773 | grep LISTEN

@@ Line 15: / Line 15: @@
 Every Seon daemon process saves its PID (process ID) in the database. If a value exists in the database on startup, the daemon refuses to start with the message that another daemon must be running at the moment. In some rare cases, the database information may not meet the real situation, when PIDs are saved in the database and no processes are running. In this case, you can start the daemon in 'forced' mode which overrides the PID check at daemon start.
-'''<u>Beware:</u>''' If more than one daemon is running, racing conditions occur between the different running programs, mostly leading to problems in receiving or sending files. This situation is highly unsupported and absolutely to be avoided!
+'''<u>Beware:</u>''' If more than one daemon is running, race conditions occur between the different running programs, mostly leading to problems in receiving or sending files. This situation is highly unsupported and absolutely to be avoided!
 == Identify running processes ==
 == When to start in 'forced' mode? ==

Seon check running daemons - Revision history

Admin at 07:35, 15 July 2011

Admin at 07:35, 15 July 2011

Admin at 07:29, 15 July 2011

Admin at 07:29, 15 July 2011

Admin at 07:26, 15 July 2011

Admin at 07:22, 15 July 2011

Admin at 07:16, 15 July 2011

Admin at 07:16, 15 July 2011

Admin at 07:15, 15 July 2011

Admin: New page: == Which processes must run == In order to keep Seon running, the following processes must exist: *seonrd: The Seon master receive daemon (parent process of the subsequent rec...

Admin: New page: == Which processes must run == In order to keep Seon running, the following processes must exist: *`seonrd`: The Seon master receive daemon (parent process of the subsequent rec...