Re: Problem with relayctl - OBSD 4.4
Hello, Here is the log for relayd -dv. When I try to relayctl reload I got a command failed and nothing in relayd output. # relayd -dv warning: macro 'squid_adh' not used warning: macro 'dns_adh' not used warning: macro 'dns1_ext' not used warning: macro 'dns2_ext' not used warning: macro 'mx1_ext' not used warning: macro 'mx2_ext' not used warning: macro 'mx_int' not used warning: macro 'mx_adh' not used startup relay_privinit: adding relay squid protocol 1: name http_proxy flags: 0x0004 type: http relay_privinit: adding relay dns protocol 2: name dnsfilter flags: 0x0004 type: hce_notify_done: 10.60.0.102 (tcp_host_up: connect successful) host 10.60.0.102, check tcp (1ms), state unknown - up, availability 100.00% hce_notify_done: 10.60.0.102 (tcp_host_up: connect successful) host 10.60.0.102, check tcp (1ms), state unknown - up, availability 100.00% hce_notify_done: 10.60.0.101 (tcp_host_up: connect successful) host 10.60.0.101, check tcp (1ms), state unknown - up, availability 100.00% hce_notify_done: 10.60.0.101 (tcp_host_up: connect successful) host 10.60.0.101, check tcp (1ms), state unknown - up, availability 100.00% dns relay_init: max open files 1024 adding 2 hosts from table squid:3128 adding 2 hosts from table DNS:53 relay_init: max open files 1024 relay_init: max open files 1024 relay_init: max open files 1024 relay_init: max open files 1024 relay_init: max open files 1024 relay_init: max open files 1024 relay_init: max open files 1024 relay_init: max open files 1024 init_filter: filter init done relay_launch: running relay squid adding 2 hosts from table squid:3128 adding 2 hosts from table squid:3128 adding 2 hosts from table squid:3128 adding 2 hosts from table squid:3128 adding 2 hosts from table squid:3128 adding 2 hosts from table squid:3128 adding 2 hosts from table squid:3128 adding 2 hosts from table squid:3128 relay_init: max open files 1024 init_tables: created 0 tables adding 2 hosts from table DNS:53 adding 2 hosts from table DNS:53 adding 2 hosts from table DNS:53 adding 2 hosts from table DNS:53 adding 2 hosts from table DNS:53 adding 2 hosts from table DNS:53 adding 2 hosts from table DNS:53 adding 2 hosts from table DNS:53 adding 2 hosts from table squid:3128 pfe_dispatch_imsg: state 1 for host 2 10.60.0.102 relay_launch: running relay squid adding 2 hosts from table DNS:53 relay_launch: running relay squid relay_launch: running relay squid relay_launch: running relay squid relay_launch: running relay squid relay_launch: running relay dns relay_launch: running relay dns pfe_dispatch_imsg: state 1 for host 4 10.60.0.102 relay_launch: running relay squid relay_launch: running relay dns relay_launch: running relay squid relay_launch: running relay squid relay_launch: running relay dns relay_launch: running relay dns relay_launch: running relay dns pfe_dispatch_imsg: state 1 for host 1 10.60.0.101 relay_launch: running relay dns relay_launch: running relay dns relay_launch: running relay dns relay_launch: running relay squid pfe_dispatch_imsg: state 1 for host 3 10.60.0.101 relay_launch: running relay dns hce_notify_done: 10.60.0.101 (tcp_host_up: connect successful) hce_notify_done: 10.60.0.101 (tcp_host_up: connect successful) hce_notify_done: 10.60.0.102 (tcp_host_up: connect successful) hce_notify_done: 10.60.0.102 (tcp_host_up: connect successful) -- Cordialement, Pierre BARDOU -Message d'origine- De : Stuart Henderson [mailto:[EMAIL PROTECTED] Envoyé : mardi 11 novembre 2008 13:20 À : misc@openbsd.org Objet : Re: Problem with relayctl - OBSD 4.4 On 2008-11-11, James Records [EMAIL PROTECTED] wrote: Pierre, I'm seeing the same exact thing, I'm not able to reload the config without killing and restarting relayd. I haven't looked at the source yet, but I may get to that in the next couple days, restarting is an ok work around for me at this point, but won't be when it gets into production. Jim Run relayd -dv, try and reload the config, check the output and paste it in mail. BEGIN:VCARD VERSION:2.1 N:Bardou;Pierre FN:BARDOU Pierre ADR;WORK:;B011 LABEL;WORK:B011 EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20070806T072621Z END:VCARD smime.p7s Description: S/MIME cryptographic signature
Re: Problem with relayctl - OBSD 4.4
On 2008-Nov-11, at 10:13 AM, Stuart Henderson wrote: I should probably have also mentioned to mark the point where relayctl reload is run.. Right before ^Chost check engine exiting When relayctl returns command failed. nothing appears in the debugging output. Derek
Re: Problem with relayctl - OBSD 4.4
On 2008-11-11, Derek Buttineau [EMAIL PROTECTED] wrote: Run relayd -dv, try and reload the config, check the output and paste it in mail. I should probably have also mentioned to mark the point where relayctl reload is run.. I get the same thing as well when trying to reload via relayctl, says command failed. I am still also unable to get transparent relaying working. I assume that though is more me missing something from my configuration (see my post subject Transparent Reverse Proxy with relayd for the config). Here's my output from relayd -dv = startup relay_privinit: adding relay pop3 protocol 1: name tcp_service flags: 0x0004 type: tcp relay_privinit: adding relay pop3s protocol 1: name tcp_service flags: 0x0004 type: tcp relay_privinit: adding relay imap protocol 1: name tcp_service flags: 0x0004 type: tcp relay_privinit: adding relay imaps protocol 1: name tcp_service flags: 0x0004 type: tcp relay_privinit: adding relay maildelivery protocol 1: name tcp_service flags: 0x0004 type: tcp relay_init: max open files 1024 adding 2 hosts from table pop3_servers:110 adding 2 hosts from table pop3_servers:995 adding 2 hosts from table pop3_servers:143 adding 2 hosts from table pop3_servers:993 adding 2 hosts from table pop3_servers:25 relay_init: max open files 1024 relay_init: max open files 1024 adding 2 hosts from table pop3_servers:110 adding 2 hosts from table pop3_servers:995 adding 2 hosts from table pop3_servers:143 adding 2 hosts from table pop3_servers:993 relay_init: max open files 1024 adding 2 hosts from table pop3_servers:25 adding 2 hosts from table pop3_servers:110 adding 2 hosts from table pop3_servers:995 adding 2 hosts from table pop3_servers:143 relay_init: max open files 1024 adding 2 hosts from table pop3_servers:993 adding 2 hosts from table pop3_servers:25 adding 2 hosts from table pop3_servers:110 adding 2 hosts from table pop3_servers:995 adding 2 hosts from table pop3_servers:143 adding 2 hosts from table pop3_servers:993 adding 2 hosts from table pop3_servers:25 hce_notify_done: 10.10.19.4 (tcp_host_up: connect successful) relay_launch: running relay pop3 relay_launch: running relay pop3 relay_launch: running relay pop3s relay_launch: running relay imap relay_launch: running relay imaps relay_launch: running relay maildelivery relay_launch: running relay pop3 relay_launch: running relay pop3s relay_launch: running relay imap relay_launch: running relay imaps relay_launch: running relay maildelivery relay_launch: running relay pop3 relay_launch: running relay pop3s relay_launch: running relay imap relay_launch: running relay imaps relay_launch: running relay maildelivery relay_init: max open files 1024 adding 2 hosts from table pop3_servers:110 adding 2 hosts from table pop3_servers:995 adding 2 hosts from table pop3_servers:143 adding 2 hosts from table pop3_servers:993 adding 2 hosts from table pop3_servers:25 relay_launch: running relay pop3s host 10.10.19.4, check tcp (6ms), state unknown - up, availability 100.00% hce_notify_done: 10.10.19.5 (tcp_host_up: connect successful) host 10.10.19.5, check tcp (6ms), state unknown - up, availability 100.00% hce_notify_done: 10.10.19.4 (tcp_host_up: connect successful) host 10.10.19.4, check tcp (6ms), state unknown - up, availability 100.00% hce_notify_done: 10.10.19.5 (tcp_host_up: connect successful) host 10.10.19.5, check tcp (6ms), state unknown - up, availability 100.00% hce_notify_done: 10.10.19.4 (tcp_host_up: connect successful) host 10.10.19.4, check tcp (7ms), state unknown - up, availability 100.00% hce_notify_done: 10.10.19.5 (tcp_host_up: connect successful) host 10.10.19.5, check tcp (7ms), state unknown - up, availability 100.00% hce_notify_done: 10.10.19.4 (tcp_host_up: connect successful) host 10.10.19.4, check tcp (7ms), state unknown - up, availability 100.00% hce_notify_done: 10.10.19.5 (tcp_host_up: connect successful) host 10.10.19.5, check tcp (7ms), state unknown - up, availability 100.00% hce_notify_done: 10.10.19.4 (tcp_host_up: connect successful) host 10.10.19.4, check tcp (7ms), state unknown - up, availability 100.00% hce_notify_done: 10.10.19.5 (tcp_host_up: connect successful) host 10.10.19.5, check tcp (7ms), state unknown - up, availability 100.00% relay_init: max open files 1024 adding 2 hosts from table pop3_servers:110 adding 2 hosts from table pop3_servers:995 adding 2 hosts from table pop3_servers:143 relay_init: max open files 1024 adding 2 hosts from table pop3_servers:110 adding 2 hosts from table pop3_servers:995 adding 2 hosts from table pop3_servers:993 adding 2 hosts from table pop3_servers:143 adding 2 hosts from table pop3_servers:993 relay_launch: running relay pop3 relay_launch: running relay pop3s relay_launch: running
Re: Problem with relayctl - OBSD 4.4
On 2008-11-11, James Records [EMAIL PROTECTED] wrote: Pierre, I'm seeing the same exact thing, I'm not able to reload the config without killing and restarting relayd. I haven't looked at the source yet, but I may get to that in the next couple days, restarting is an ok work around for me at this point, but won't be when it gets into production. Jim Run relayd -dv, try and reload the config, check the output and paste it in mail.
Re: Problem with relayctl - OBSD 4.4
Run relayd -dv, try and reload the config, check the output and paste it in mail. I get the same thing as well when trying to reload via relayctl, says command failed. I am still also unable to get transparent relaying working. I assume that though is more me missing something from my configuration (see my post subject Transparent Reverse Proxy with relayd for the config). Here's my output from relayd -dv = startup relay_privinit: adding relay pop3 protocol 1: name tcp_service flags: 0x0004 type: tcp relay_privinit: adding relay pop3s protocol 1: name tcp_service flags: 0x0004 type: tcp relay_privinit: adding relay imap protocol 1: name tcp_service flags: 0x0004 type: tcp relay_privinit: adding relay imaps protocol 1: name tcp_service flags: 0x0004 type: tcp relay_privinit: adding relay maildelivery protocol 1: name tcp_service flags: 0x0004 type: tcp relay_init: max open files 1024 adding 2 hosts from table pop3_servers:110 adding 2 hosts from table pop3_servers:995 adding 2 hosts from table pop3_servers:143 adding 2 hosts from table pop3_servers:993 adding 2 hosts from table pop3_servers:25 relay_init: max open files 1024 relay_init: max open files 1024 adding 2 hosts from table pop3_servers:110 adding 2 hosts from table pop3_servers:995 adding 2 hosts from table pop3_servers:143 adding 2 hosts from table pop3_servers:993 relay_init: max open files 1024 adding 2 hosts from table pop3_servers:25 adding 2 hosts from table pop3_servers:110 adding 2 hosts from table pop3_servers:995 adding 2 hosts from table pop3_servers:143 relay_init: max open files 1024 adding 2 hosts from table pop3_servers:993 adding 2 hosts from table pop3_servers:25 adding 2 hosts from table pop3_servers:110 adding 2 hosts from table pop3_servers:995 adding 2 hosts from table pop3_servers:143 adding 2 hosts from table pop3_servers:993 adding 2 hosts from table pop3_servers:25 hce_notify_done: 10.10.19.4 (tcp_host_up: connect successful) relay_launch: running relay pop3 relay_launch: running relay pop3 relay_launch: running relay pop3s relay_launch: running relay imap relay_launch: running relay imaps relay_launch: running relay maildelivery relay_launch: running relay pop3 relay_launch: running relay pop3s relay_launch: running relay imap relay_launch: running relay imaps relay_launch: running relay maildelivery relay_launch: running relay pop3 relay_launch: running relay pop3s relay_launch: running relay imap relay_launch: running relay imaps relay_launch: running relay maildelivery relay_init: max open files 1024 adding 2 hosts from table pop3_servers:110 adding 2 hosts from table pop3_servers:995 adding 2 hosts from table pop3_servers:143 adding 2 hosts from table pop3_servers:993 adding 2 hosts from table pop3_servers:25 relay_launch: running relay pop3s host 10.10.19.4, check tcp (6ms), state unknown - up, availability 100.00% hce_notify_done: 10.10.19.5 (tcp_host_up: connect successful) host 10.10.19.5, check tcp (6ms), state unknown - up, availability 100.00% hce_notify_done: 10.10.19.4 (tcp_host_up: connect successful) host 10.10.19.4, check tcp (6ms), state unknown - up, availability 100.00% hce_notify_done: 10.10.19.5 (tcp_host_up: connect successful) host 10.10.19.5, check tcp (6ms), state unknown - up, availability 100.00% hce_notify_done: 10.10.19.4 (tcp_host_up: connect successful) host 10.10.19.4, check tcp (7ms), state unknown - up, availability 100.00% hce_notify_done: 10.10.19.5 (tcp_host_up: connect successful) host 10.10.19.5, check tcp (7ms), state unknown - up, availability 100.00% hce_notify_done: 10.10.19.4 (tcp_host_up: connect successful) host 10.10.19.4, check tcp (7ms), state unknown - up, availability 100.00% hce_notify_done: 10.10.19.5 (tcp_host_up: connect successful) host 10.10.19.5, check tcp (7ms), state unknown - up, availability 100.00% hce_notify_done: 10.10.19.4 (tcp_host_up: connect successful) host 10.10.19.4, check tcp (7ms), state unknown - up, availability 100.00% hce_notify_done: 10.10.19.5 (tcp_host_up: connect successful) host 10.10.19.5, check tcp (7ms), state unknown - up, availability 100.00% relay_init: max open files 1024 adding 2 hosts from table pop3_servers:110 adding 2 hosts from table pop3_servers:995 adding 2 hosts from table pop3_servers:143 relay_init: max open files 1024 adding 2 hosts from table pop3_servers:110 adding 2 hosts from table pop3_servers:995 adding 2 hosts from table pop3_servers:993 adding 2 hosts from table pop3_servers:143 adding 2 hosts from table pop3_servers:993 relay_launch: running relay pop3 relay_launch: running relay pop3s relay_launch: running relay imap relay_launch: running relay imaps adding 2 hosts from table pop3_servers:25 relay_launch: running relay maildelivery adding 2 hosts from table pop3_servers:25 relay_launch: running relay imap adding 2 hosts from table pop3_servers:110 init_filter:
Re: Problem with relayctl - OBSD 4.4
Pierre, I'm seeing the same exact thing, I'm not able to reload the config without killing and restarting relayd. I haven't looked at the source yet, but I may get to that in the next couple days, restarting is an ok work around for me at this point, but won't be when it gets into production. Jim 2008/11/7 BARDOU Pierre [EMAIL PROTECTED] Hello, I have something which looks like a bug using relayctl on openBSD 4.4 : * My config file is correct according to relayd -n * I can launch relayd * I can't reload the config file using relayctl reload : it says command failed /var/log/daemon.log and /var/log/messages don't report anything Someone knows about this problem ? Thank you -- Cordialement, Pierre BARDOU CSIM - Bureau 012 Midi Pyrinies Informatique Hospitalihre 12 rue Michel Labrousse BP93668 F-31036 Toulouse CEDEX 1 Til : 05 67 31 90 84 Fax : 05 34 61 51 00 Mail : [EMAIL PROTECTED]
Problem with relayctl - OBSD 4.4
Hello, I have something which looks like a bug using relayctl on openBSD 4.4 : * My config file is correct according to relayd -n * I can launch relayd * I can't reload the config file using relayctl reload : it says command failed /var/log/daemon.log and /var/log/messages don't report anything Someone knows about this problem ? Thank you -- Cordialement, Pierre BARDOU CSIM - Bureau 012 Midi Pyrénées Informatique Hospitalière 12 rue Michel Labrousse BP93668 F-31036 Toulouse CEDEX 1 Tél : 05 67 31 90 84 Fax : 05 34 61 51 00 Mail : [EMAIL PROTECTED] BEGIN:VCARD VERSION:2.1 N:Bardou;Pierre FN:BARDOU Pierre ADR;WORK:;B011 LABEL;WORK:B011 EMAIL;PREF;INTERNET:[EMAIL PROTECTED] REV:20070806T072621Z END:VCARD smime.p7s Description: S/MIME cryptographic signature
