[7.450][QUESTION][ANSWERED] Sockd continually restarting

[RFCat_vk]

Hi,
I have been receiving e-mails about sockd not running and being restarted about 10 or a day.

More of a nuisance with the effective junk mail. I know I can disable the sending of the message, but that doesn't address the issue of why sockd is failing.

Ian M

[BAlfson]

Not using socks proxy, so I don't see this.

Cheers - Bob

[RFCat_vk]

Hi Bob,
the error message pops up approx every hour.

Ian M

[nitehawk]

Hi Ian

what says the /var/log/sockd.log - is there any useful information in there?

Cheers
nitehawk

[RFCat_vk]

Hi nitehawk,
I have just put the v7.450b back on line.

I am looking through the archived logs and the only thing I can see are what I would call error packets, the IP address has changed to 0.0.0.1 instead of 192.168.10.1.

I will leave the system running as long as possible today to refresh the logs.

2009:06:05-10:42:58 fw1-on-house sockd[715]: pass(4): tcp/connect [: 192.168.10.250.1042 -> 207.46.124.147.1863
2009:06:05-10:42:58 fw1-on-house sockd[716]: pass(4): tcp/connect [: 192.168.10.250.1043 -> 207.46.124.147.1863
2009:06:05-10:48:11 fw1-on-house sockd[714]: pass(1): tcp/accept [: 192.168.10.250.1124 -> 192.168.10.1.1080
2009:06:05-10:48:11 fw1-on-house sockd[714]: pass(1): tcp/accept [: 192.168.10.250.1123 -> 192.168.10.1.1080
2009:06:05-10:48:11 fw1-on-house sockd[716]: pass(4): tcp/connect [: 192.168.10.250.1123 -> 0.0.0.1.1863
2009:06:05-10:48:11 fw1-on-house sockd[716]: pass(4): tcp/connect ]: 192.168.10.250.1123 -> 0.0.0.1.1863: Invalid argument

But this doesn't happen all the time, not like the e-mail messages I was receiving.

Ian M

[RFCat_vk]

Hi Folks,

I found this about the the same time as the e-mail advising that sockd wasn't running. The e-mail was dated 14/6/2009 1109. There isn't any messages in the socks log.

Ian M

2009:06:14-11:08:56 fw1-on-house notifier[3054]: INFO: #------------------ notification start -------------------#
2009:06:14-11:08:56 fw1-on-house notifier[3054]: INFO: #-- Received notification request for INFO-120
2009:06:14-11:08:56 fw1-on-house notifier[3054]: INFO: trap: status off or no trapsinks configured
2009:06:14-11:08:56 fw1-on-house notifier[3054]: INFO: == sending notfication via mail!
2009:06:14-11:08:56 fw1-on-house notifier[3054]: INFO: #-- Success: sent notification INFO-120!
2009:06:14-11:08:56 fw1-on-house notifier[3054]: INFO: #------------------ notification end -------------------#
2009:06:14-11:50:02 fw1-on-house notifier[3054]: INFO: #------------------ notification start -------------------#
2009:06:14-11:50:02 fw1-on-house notifier[3054]: INFO: #-- Received notification request for INFO-005
2009:06:14-11:50:02 fw1-on-house notifier[3054]: INFO: trap: status off or no trapsinks configured
2009:06:14-11:50:02 fw1-on-house notifier[3054]: INFO: #------------------ notification end -------------------#

2009:06:14-11:08:40 fw1-on-house selfmonng[3271]: W triggerAction: 'cmd'
2009:06:14-11:08:40 fw1-on-house selfmonng[3271]: W actionCmd(-): '/var/mdw/scripts/socks restart'
2009:06:14-11:08:45 fw1-on-house selfmonng[3271]: I check Failed increment sockd_running counter 1 - 3
2009:06:14-11:08:50 fw1-on-house selfmonng[3271]: I check Failed increment sockd_running counter 2 - 3
2009:06:14-11:08:55 fw1-on-house selfmonng[3271]: W check Failed increment sockd_running counter 3 - 3
2009:06:14-11:08:55 fw1-on-house selfmonng[3271]: Sockd not running - restarted
2009:06:14-11:08:55 fw1-on-house selfmonng[3271]: W NOTIFYEVENT Name=sockd_running Level=INFO Id=120 sent
2009:06:14-11:08:55 fw1-on-house selfmonng[3271]: W triggerAction: 'cmd'
2009:06:14-11:08:55 fw1-on-house selfmonng[3271]: W actionCmd(+): '/var/mdw/scripts/socks restart'
2009:06:14-11:08:55 fw1-on-house selfmonng[3271]: W child returned status: exit='1' signal='0'
2009:06:14-11:09:00 fw1-on-house selfmonng[3271]: I check Failed increment sockd_running counter 1 - 3
2009:06:14-11:09:05 fw1-on-house selfmonng[3271]: I check Failed increment sockd_running counter 2 - 3
2009:06:14-11:09:10 fw1-on-house selfmonng[3271]: W check Failed increment sockd_running counter 3 - 3
2009:06:14-11:09:10 fw1-on-house selfmonng[3271]: W NOTIFYEVENT Name=sockd_running Level=INFO Id=120 suppressed

[Astaro Beta Bot]

Astaro Beta Report
--------------------------------
Version: 7.450
Type: QUESTION
State: ANSWERED
Reporter: RFCat_vk
Contributor: 
MantisID: 
--------------------------------

[RFCat_vk]

Hi,
since I put the Intel Atom 330 box back on line yesterday I have been receiving a sockd restarted warning every hour. I stopped the sockd proxy for a while then restarted, it to no effect.
I have checked the sockd.log and it is empty, null.

But the admin notifications log has entries in it. Please see below.

Ian M

2009:06:28-06:28:38 fw1-on-house notifier[3119]: INFO: #------------------ notification end -------------------#
2009:06:28-07:23:58 fw1-on-house notifier[3119]: INFO: #------------------ notification start -------------------#
2009:06:28-07:23:58 fw1-on-house notifier[3119]: INFO: #-- Received notification request for INFO-120
2009:06:28-07:23:58 fw1-on-house notifier[3119]: INFO: trap: status off or no trapsinks configured
2009:06:28-07:23:58 fw1-on-house notifier[3119]: INFO: == sending notfication via mail!
2009:06:28-07:23:59 fw1-on-house notifier[3119]: INFO: #-- Success: sent notification INFO-120!
2009:06:28-07:23:59 fw1-on-house notifier[3119]: INFO: #------------------ notification end -------------------#
2009:06:28-08:30:06 fw1-on-house notifier[3119]: INFO: #------------------ notification start -------------------#
2009:06:28-08:30:06 fw1-on-house notifier[3119]: INFO: #-- Received notification request for INFO-120
2009:06:28-08:30:06 fw1-on-house notifier[3119]: INFO: trap: status off or no trapsinks configured
2009:06:28-08:30:06 fw1-on-house notifier[3119]: INFO: == sending notfication via mail!
2009:06:28-08:30:06 fw1-on-house notifier[3119]: INFO: #-- Success: sent notification INFO-120!
2009:06:28-08:30:06 fw1-on-house notifier[3119]: INFO: #------------------ notification end -------------------#
2009:06:28-09:25:12 fw1-on-house notifier[3119]: INFO: #------------------ notification start -------------------#
2009:06:28-09:25:12 fw1-on-house notifier[3119]: INFO: #-- Received notification request for INFO-120
2009:06:28-09:25:12 fw1-on-house notifier[3119]: INFO: trap: status off or no trapsinks configured
2009:06:28-09:25:12 fw1-on-house notifier[3119]: INFO: == sending notfication via mail!
2009:06:28-09:25:12 fw1-on-house notifier[3119]: INFO: #-- Success: sent notification INFO-120!
2009:06:28-09:25:12 fw1-on-house notifier[3119]: INFO: #------------------ notification end -------------------#
2009:06:28-09:40:11 fw1-on-house notifier[3119]: INFO: #------------------ notification start -------------------#
2009:06:28-09:40:11 fw1-on-house notifier[3119]: INFO: #-- Received notification request for INFO-005
2009:06:28-09:40:11 fw1-on-house notifier[3119]: INFO: trap: status off or no trapsinks configured
2009:06:28-09:40:11 fw1-on-house notifier[3119]: INFO: #------------------ notification end -------------------#

[Billybob]

I don't use socks proxy for anything, but fired up socks and running msn messenger via socks just to test.
So far I do get the error message mentioned by Ian

2009:06:28-10:59:40 gatekeeper sockd[27787]: pass(4): tcp/connect ]: 192.168.0.10.54965 -> 0.0.0.1.1863: Invalid argument

Will see how stable it is and report back.

[andyk007]

is there still a problem with socks in version 7.470 I cannot reproduce any error message

greetings
Andreas