SYSTEM WARNING: 'date_default_timezone_get(): It is not safe to rely on the system's timezone settings. You are *required* to use the date.timezone setting or the date_default_timezone_set() function. In case you used any of those methods and you are still getting this warning, you most likely misspelled the timezone identifier. We selected the timezone 'UTC' for now, but please set date.timezone to select your timezone.' in '/usr/share/mantis/www/core.php' line 264

0000512: dnsmasq will not be started on boot - MantisBT
MantisBT - Endian Firewall
View Issue Details
0000512Endian FirewallOther Servicespublic2008-01-24 15:052010-11-22 11:49
peter-endian 
peter-endian 
normalminorhave not tried
closedfixed 
2.2-beta2 
2.4.12.4 
0000512: dnsmasq will not be started on boot
dnsmasq will not be started on boot
No tags attached.
Issue History
2008-01-24 15:05peter-endianNew Issue
2008-01-24 15:05peter-endianTarget Version => 2.2-beta3
2008-01-24 15:43peter-endianSummary/etc/init.d/dnsmasq status is missing => dnsmasq will not be started on boot
2008-01-24 15:43peter-endianDescription Updated
2008-01-24 16:12peter-endianNote Added: 0000848
2008-01-30 11:31ra-endianStatusnew => closed
2008-01-30 11:31ra-endianResolutionopen => unable to reproduce
2009-07-27 13:31sudsNote Added: 0002793
2009-07-27 13:31sudsStatusclosed => feedback
2009-07-27 13:31sudsResolutionunable to reproduce => reopened
2009-07-27 13:32sudsNote Edited: 0002793
2009-07-28 03:54sudsNote Added: 0002800
2010-09-20 18:27peter-endianTarget Version2.2-beta3 => 2.4.1
2010-09-23 16:17peter-endianStatusfeedback => acknowledged
2010-09-24 14:45peter-endianStatusacknowledged => resolved
2010-09-24 14:45peter-endianFixed in Version => 2.4
2010-09-24 14:45peter-endianResolutionreopened => fixed
2010-09-24 14:45peter-endianAssigned To => peter-endian
2010-11-22 11:49peter-endianStatusresolved => closed

Notes
(0000848)
peter-endian   
2008-01-24 16:12   
cannot reproduce.. seems that this happens only some times
maybe related with uplinksdaemon hook. (will be restarted in addrchanged and in mainchanged, maybe that's the problem)
(0002793)
suds   
2009-07-27 13:31   
(edited on: 2009-07-27 13:32)
My observation :

EndianVersion :

2.6.22.19-72.endian
Endian Firewall Community release 2.2


Its something to do with the order of start..
40blackholedns
40dnsmasq
40httpd
40openvpn
40ssh

In /etc/rc.d/start I changed 40dnsmasq to 45dnsmasq.
rebooted the endian..
This message "failed to load names from /etc/openvpn/dnsmasq.hosts.conf: No such file or directory" does not appear.


now I see this error :
Jul 27 18:53:21 endian sudo: root : TTY=unknown ; PWD=/ ; USER=root ; COMMAND=/usr/local/bin/restartdnsmasq.py --resolv-only

(0002800)
suds   
2009-07-28 03:54   
I rebooted to test.. still it was not starting..
then I created the file : touch /etc/openvpn/dnsmasq.hosts.conf

now on reboot dnsmasq is starting.