Author Topic: snort! or not  (Read 2475 times)

JPB

  • Zen Monk
  • **
  • Posts: 77
  • Karma: +1/-1
    • View Profile
snort! or not
« on: February 28, 2011, 03:47:12 pm »
root@chaos:~# tail -vf /var/log/ebox/ebox.log
==> /var/log/ebox/ebox.log <==
2011/02/28 16:34:21 INFO> Base.pm:151 EBox::Module::Base::save - Restarting service for module: logs
2011/02/28 16:35:46 INFO> Service.pm:706 EBox::Module::Service::restartService -
Code: [Select]
Restarting service for module: ids
2011/02/28 16:35:47 ERROR> Sudo.pm:212 EBox::Sudo::_rootError - root command /etc/init.d/snort status failed.
Error output:
Command output:  * Status of snort daemon(s)
    ...fail!
.
Exit value: 3
^C
root@chaos:~# /etc/init.d/snort status
 * Status of snort daemon(s)
                                   

 ???HMM ... I wonder, looks to me that Zentayl cant restart snort but command line root user can!  I changed the IP number of one eth2 (2nd Internet Gateway) I do loadbalance shaping and failover.  what I Did not do was follow an procedure to undo the first settings and then remake the new.  If it is required for me to first remove all relational settings for an interface/gateway before reconfiguring, then i'd say Zentyal team has much more work cut out for them.  Zentyal can't expect the average user to predict the errors caused by changes of configuration.  Zentyal will need to think undo/redo and changes trough.