Modify

Opened 5 years ago

Last modified 5 years ago

#13831 reopened defect

Logging not working

Reported by: anonymous Owned by: developers
Priority: normal Milestone: Chaos Calmer 15.05
Component: base system Version: Trunk
Keywords: Cc:

Description

After the update to the last trunk (before i used r35097) it seems logging it's not working.
File /var/log/messages doesn't exists.
Here is my /etc/config/system

config 'system'
	option 'hostname'	'OpenWRT'
	option 'timezone'	'CET-1CEST,M3.5.0,M10.5.0/3'
	option 'log_file' '/var/log/messages'
	option 'log_size' '256'
	option 'log_type' 'file'	
config 'rdate'
	option 'interface'	'wan'
	
config 'led'
	option 'sysfs' 'ubnt:green:dome'
	option 'dev' 'wlan0'
	option 'mode' 'tx rx'
	option 'trigger' 'netdev'
	
config 'led'
	option 'sysfs' 'ubnt:orange:dome'
	option 'dev' 'wlan0'
	option 'mode' 'link'
	option 'trigger' 'netdev'

Attachments (0)

Change History (9)

comment:1 follow-up: Changed 5 years ago by blogic

  • Resolution set to fixed
  • Status changed from new to closed

please retry [37206] or newer

comment:2 follow-up: Changed 5 years ago by anonymous

  • Resolution fixed deleted
  • Status changed from closed to reopened

Remote log does not work at r37191

comment:3 in reply to: ↑ 2 Changed 5 years ago by anonymous

Sorry r37207

Replying to anonymous:

Remote log does not work at r37191

comment:4 follow-up: Changed 5 years ago by blogic

  • Resolution set to too_vague
  • Status changed from reopened to closed

am i supposed to guess what "does not work" mean ?

comment:5 in reply to: ↑ 4 ; follow-up: Changed 5 years ago by anonymous

OK. Sorry.

config 'system'
        option 'hostname' 'owrt'
        option 'zonename' ***'
        option 'timezone' '***'
        option 'conloglevel' '8'
        option 'cronloglevel' '8'
        option 'log_ip' '192.168.3.10'
        option 'log_port' '514'

Remote log worked before but stops in past. r37207 does not send any packets to log server. Checked as well with tcpdump for to be 100% sure.

Replying to blogic:

am i supposed to guess what "does not work" mean ?

comment:6 in reply to: ↑ 1 Changed 5 years ago by anonymous

Replying to blogic:

please retry [37206] or newer

I'll retry as soon as possible, right now i'm busy :/ .
I'll let you know if all is fine.
Thank you for the fast fix.

comment:7 in reply to: ↑ 5 Changed 5 years ago by anonymous

  • Resolution too_vague deleted
  • Status changed from closed to reopened

I know there were no changes in logging but remote log issue confirmed for r37376.
Thank you.

Replying to anonymous:

OK. Sorry.

config 'system'
        option 'hostname' 'owrt'
        option 'zonename' ***'
        option 'timezone' '***'
        option 'conloglevel' '8'
        option 'cronloglevel' '8'
        option 'log_ip' '192.168.3.10'
        option 'log_port' '514'

Remote log worked before but stops in past. r37207 does not send any packets to log server. Checked as well with tcpdump for to be 100% sure.

Replying to blogic:

am i supposed to guess what "does not work" mean ?

comment:8 Changed 5 years ago by John Allen <john@…>

"does not work" means that while the information, is being logged it is showing up in the system log. It is not being transmitted/transferred to the remote host, which in my case is a log analyzer.

config 'system'
        ...
        option 'conloglevel' '8'
        option 'cronloglevel' '8'
        option 'log_ip' '192.168.30.16'
        option 'log_port' '514'

comment:9 Changed 5 years ago by anonymous

this ticket should probably be renamed "remote logging not working"

Add Comment

Modify Ticket

Action
as reopened .
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.