More info:
it seems that upstart "think" the job is running, but not. syslog-ng doesn't
started and send the error:
"Error resolving hostname; host='xxxxxxxxx'
No destination address set;"
(xxx the name of the remote loghost)
"initctl list" show syslog-ng job as started but without pid.
We have a complex network configuration whith VLAN and Direct routing (i
have masqued the real public IP adress with XXX_MASQUED_IP_XXX on the
lo:243 interface):
eth0 Link encap:Ethernet HWaddr 00:22:64:a2:89:72
inet6 addr: fe80::222:64ff:fea2:8972/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1820469 errors:0 dropped:0 overruns:0 frame:0
TX packets:1178910 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2360570249 (2.3 GB) TX bytes:115768332 (115.7 MB)
Interrupt:16 Memory:fa000000-fa012800
eth1 Link encap:Ethernet HWaddr 00:22:64:a2:89:82
inet addr:172.17.153.10 Bcast:172.17.153.63 Mask:255.255.255.192
inet6 addr: fe80::222:64ff:fea2:8982/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:492 errors:0 dropped:0 overruns:0 frame:0
TX packets:2479 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:31488 (31.4 KB) TX bytes:754743 (754.7 KB)
Interrupt:16 Memory:f6000000-f6012800
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:4960 errors:0 dropped:0 overruns:0 frame:0
TX packets:4960 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:793400 (793.4 KB) TX bytes:793400 (793.4 KB)
lo:243 Link encap:Local Loopback
inet addr:XXX_MASQUED_IP_XXX Mask:255.255.255.255
UP LOOPBACK RUNNING MTU:16436 Metric:1
vlan200 Link encap:Ethernet HWaddr 00:22:64:a2:89:72
inet addr:10.234.53.10 Bcast:10.234.53.63 Mask:255.255.255.192
inet6 addr: fe80::222:64ff:fea2:8972/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1820475 errors:0 dropped:0 overruns:0 frame:0
TX packets:1171695 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2320520333 (2.3 GB) TX bytes:103167895 (103.1 MB)
vlan201 Link encap:Ethernet HWaddr 00:22:64:a2:89:72
inet addr:172.16.153.10 Bcast:172.16.153.63 Mask:255.255.255.192
inet6 addr: fe80::222:64ff:fea2:8972/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:6 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:468 (468.0 B)
We have access to resolver when vlan201 is UP. If i change the "start
on" with:
start on (local-filesystems and net-device-up IFACE=vlan201)
job is started. But it's not a solution for us, we are in production
with many server and many vlan. We can't have specific upstart script
for each server.
I have try:
start on net-device-up
like mountall-net, but same issue.
** Also affects: upstart
Importance: Undecided
Status: New
--
syslog-ng fails to start when using a remote loghost
https://bugs.launchpad.net/bugs/533059
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
