Thread Info
  • State Not Answered
  • Replies 9 replies
  • Subscribers 0 subscribers
  • Views 1055 views
  • Users 0 members are here
Options
Suggested

[7.470][BUG][FIXED] not sure what it is though

RFCat_vk_01
Hi,
while investigating sockd issues I found this.

2009:07:11-09:46:35 fw1-on-house middleware[3320]: |=========================================================================
2009:07:11-09:46:35 fw1-on-house middleware[3320]: E Not enough arguments!
2009:07:11-09:46:35 fw1-on-house middleware[3320]: 
2009:07:11-09:46:35 fw1-on-house middleware[3320]:  1. core::Ressource::getConfdObject:233() /PerlApp/core/Ressource.pm
2009:07:11-09:46:35 fw1-on-house middleware[3320]:  2. modules::IPTables::Adapters::nat_masq::generateRules:231() /PerlApp/modules/IPTables/Adapters/nat_masq.pm
2009:07:11-09:46:35 fw1-on-house middleware[3320]:  3. modules::IPTables::Adapter::generateAll:123() /PerlApp/modules/IPTables/Adapter.pm
2009:07:11-09:46:35 fw1-on-house middleware[3320]:  4. modules::IPTables::Adapter::load:86() /PerlApp/modules/IPTables/Adapter.pm
2009:07:11-09:46:35 fw1-on-house middleware[3320]:  5. modules::IPTables::Adapters::nat_masq::load:45() /PerlApp/modules/IPTables/Adapters/nat_masq.pm
2009:07:11-09:46:35 fw1-on-house middleware[3320]:  6. core::Config::load:279() /PerlApp/core/Config.pm
2009:07:11-09:46:35 fw1-on-house middleware[3320]:  7. main::top-level:177() mdw_deamon.pl
2009:07:11-09:46:36 fw1-on-house middleware[3320]: 
Parents
  • 0
    Hi Ian and Andy,

    Andy is right, more logs are often helpful - yet, in case i get a full backtrace from /var/log/mdw.log, that's sometimes sufficient to track down the issue without knowing anything else.  It was sufficient in this case.  These backtraces contain a lot of information.


    modules::IPTables::Adapters::nat_masq::generateRules:231


    That was the decisive piece of information here - but make sure to always show the full backtrace, like you did (and not just an extract).

    Thanks,
      Ingo
Reply
  • 0
    Hi Ian and Andy,

    Andy is right, more logs are often helpful - yet, in case i get a full backtrace from /var/log/mdw.log, that's sometimes sufficient to track down the issue without knowing anything else.  It was sufficient in this case.  These backtraces contain a lot of information.


    modules::IPTables::Adapters::nat_masq::generateRules:231


    That was the decisive piece of information here - but make sure to always show the full backtrace, like you did (and not just an extract).

    Thanks,
      Ingo
Children