When starting the jabberd, the system seems to loose a process ID: Initially jabberd is running: schledermann root # ps aux | grep jabber jabber 2358 0.1 0.9 4728 1128 pts/0 S 13:26 0:03 [jabberd] jabber 2360 0.0 0.9 4332 1088 pts/0 S 13:26 0:01 [jabberd] jabber 2362 0.0 0.3 3828 464 pts/0 S 13:26 0:00 [jabberd] root 24916 0.0 0.3 1404 448 pts/1 R 14:06 0:00 grep jabber schledermann root # /etc/init.d/jabber stop * Stopping Jabber Server... [ ok ] schledermann root # ps aux | grep jabber jabber 2360 0.0 0.9 4332 1088 pts/0 S 13:26 0:01 [jabberd] root 24948 0.0 0.3 1404 444 pts/1 S 14:07 0:00 grep jabber schledermann root # /etc/init.d/jabber start * Starting Jabber Server... [ ok ] schledermann root # /etc/init.d/jabber stop * Stopping Jabber Server... [ ok ] schledermann root # ps aux | grep jabber jabber 2360 0.0 0.9 4332 1088 pts/0 S 13:26 0:01 [jabberd] jabber 25128 0.2 1.0 4020 1268 pts/1 S 14:07 0:00 [jabberd] root 25171 0.0 0.3 1404 448 pts/1 R 14:07 0:00 grep jabber schledermann root # /etc/init.d/jabber start * Starting Jabber Server... [ ok ] schledermann root # /etc/init.d/jabber stop * Stopping Jabber Server... [ ok ] schledermann root # ps aux | grep jabber jabber 2360 0.0 0.9 4336 1092 pts/0 S 13:26 0:01 [jabberd] jabber 25128 0.1 1.0 4020 1272 pts/1 S 14:07 0:00 [jabberd] jabber 25235 0.0 1.0 4020 1268 pts/1 S 14:07 0:00 [jabberd] root 25267 0.0 0.3 1404 448 pts/1 R 14:07 0:00 grep jabber schledermann root # For each jabberd restart there's a redundant jabberd process. Further the "orphan" jabberd processes appears to increase there memory footprint over time, so after having jabberd running for a 1
When starting the jabberd, the system seems to loose a process ID: Initially jabberd is running: schledermann root # ps aux | grep jabber jabber 2358 0.1 0.9 4728 1128 pts/0 S 13:26 0:03 [jabberd] jabber 2360 0.0 0.9 4332 1088 pts/0 S 13:26 0:01 [jabberd] jabber 2362 0.0 0.3 3828 464 pts/0 S 13:26 0:00 [jabberd] root 24916 0.0 0.3 1404 448 pts/1 R 14:06 0:00 grep jabber schledermann root # /etc/init.d/jabber stop * Stopping Jabber Server... [ ok ] schledermann root # ps aux | grep jabber jabber 2360 0.0 0.9 4332 1088 pts/0 S 13:26 0:01 [jabberd] root 24948 0.0 0.3 1404 444 pts/1 S 14:07 0:00 grep jabber schledermann root # /etc/init.d/jabber start * Starting Jabber Server... [ ok ] schledermann root # /etc/init.d/jabber stop * Stopping Jabber Server... [ ok ] schledermann root # ps aux | grep jabber jabber 2360 0.0 0.9 4332 1088 pts/0 S 13:26 0:01 [jabberd] jabber 25128 0.2 1.0 4020 1268 pts/1 S 14:07 0:00 [jabberd] root 25171 0.0 0.3 1404 448 pts/1 R 14:07 0:00 grep jabber schledermann root # /etc/init.d/jabber start * Starting Jabber Server... [ ok ] schledermann root # /etc/init.d/jabber stop * Stopping Jabber Server... [ ok ] schledermann root # ps aux | grep jabber jabber 2360 0.0 0.9 4336 1092 pts/0 S 13:26 0:01 [jabberd] jabber 25128 0.1 1.0 4020 1272 pts/1 S 14:07 0:00 [jabberd] jabber 25235 0.0 1.0 4020 1268 pts/1 S 14:07 0:00 [jabberd] root 25267 0.0 0.3 1404 448 pts/1 R 14:07 0:00 grep jabber schledermann root # For each jabberd restart there's a redundant jabberd process. Further the "orphan" jabberd processes appears to increase there memory footprint over time, so after having jabberd running for a 1½ day, my system was nearly bogged down.
The net-im team (which is just me at the moment) is working on a split of jabber-server into jabberd and it's individual transports as separate packages. This particular bug might be upstream, but we'll review it after the split is complete, which will hopefully be within the week.
Ok tnx I have tried to kill the extra jabberd process manually (kill -KILL <pid>). The two remaining processes does not seem to grow in size. Its been running for tree days now untouched. schledermann spamassassin # ps aux | grep jabber jabber 12744 0.0 0.8 4760 1032 ? S Jan19 0:07 [jabberd] jabber 12748 0.0 0.0 3828 0 ? SW Jan19 0:00 [jabberd]
