System logs

[sea2space]

Hello!

I run tac-plus_ng via tac_plus-ng.service

When i run it manually with -d key: "tac_plus-ng -f tac_plus-ng.cfg -d 4" i can see system events (debug)

Is it possible to run via tac_plus-ng.service and see same system events (debug) and for example write them to a file or to /var/log/messages?

[MarcJHuber]

Hi,

debug output will be written to syslog if isatty() fails for stderr. Do you see the syslog messages when running tac_plus-ng -d -4 -f tac_plus-ng.cfg 2> /dev/null?

Cheers,

Marc

[sea2space]

Hi!

Yes, i see next:

[root@aaantp1 dtest]# tac_plus-ng -d 4 -f /root/tac_plus-ng.cfg > /dev/null 
671016: 08:57:13.373 0/00000000: - Version 138db65fa8593cdaf8efdf6012d52a26380a63cf initialized
671016: 08:57:17.615 0/5986b5eb: 10.10.10.193 authen: hdr->seq_no: 1
671016: 08:57:17.615 0/5986b5eb: 10.10.10.193 looking for user dtest realm default
671016: 08:57:17.615 0/5986b5eb: 10.10.10.193 user lookup failed
671016: 08:57:17.632 0/5986b5eb: 10.10.10.193 authen: hdr->seq_no: 3
671016: 08:57:17.632 0/5986b5eb: 10.10.10.193 looking for user dtest  realm default
671016: 08:57:17.632 0/5986b5eb: 10.10.10.193 user lookup failed
671016: 08:57:17.632 0/5986b5eb: 10.10.10.193 looking for user dtest  in MAVIS backend
671016: 08:57:17.667 0/5986b5eb: 10.10.10.193 result for user dtest  is ACK [34 ms]
671016: 08:57:17.667 0/5986b5eb: 10.10.10.193 looking for user dtest  realm default
671016: 08:57:17.667 0/5986b5eb: 10.10.10.193 user lookup succeded
671016: 08:57:17.667 0/5986b5eb: 10.10.10.193 shell login for 'dtest ' from 20.20.20.138 on tty2 succeeded (profile=readwrite)

But in /var/log/messages, i see a lot of similar messages like this:

....
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669340]: scm_send_msg: sendmsg: Connection refused
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669374]: epoll event notification mechanism is being used
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669379]: epoll event notification mechanism is being used
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669374]: scm_send_msg: sendmsg: Connection refused
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669374]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669374]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669374]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669374]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669374]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669374]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669384]: epoll event notification mechanism is being used
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669374]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669379]: scm_send_msg: sendmsg: Connection refused
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669379]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669340]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669379]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669379]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669379]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669379]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669379]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669379]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669379]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669379]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669379]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669389]: epoll event notification mechanism is being used
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669384]: scm_send_msg: sendmsg: Connection refused
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669384]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669384]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669384]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669384]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669384]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669384]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669384]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:09 30.30.30.151 tac_plus-ng[669384]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:11 30.30.30.151 tac_plus-ng[669374]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:11 30.30.30.151 tac_plus-ng[669379]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:11 30.30.30.151 tac_plus-ng[669384]: scm_send_msg: sendmsg: Transport endpoint is not connected
Aug 28 08:09:12 30.30.30.151 tac_plus-ng[668782]: child (pid 669374) terminated normally
Aug 28 08:09:12 30.30.30.151 tac_plus-ng[668782]: child (pid 669379) terminated normally
Aug 28 08:09:12 30.30.30.151 tac_plus-ng[668782]: child (pid 669384) terminated normally
Aug 28 08:10:04 30.30.30.151 tac_plus-ng[668782]: child (pid 669340) terminated normally
Aug 28 08:10:12 30.30.30.151 tac_plus-ng[668782]: child (pid 669389) terminated normally
Aug 28 08:14:03 30.30.30.151 tac_plus-ng[669539]: epoll event notification mechanism is being used
Aug 28 08:15:05 30.30.30.151 tac_plus-ng[668782]: child (pid 669539) terminated normally
Aug 28 08:19:03 30.30.30.151 tac_plus-ng[669689]: epoll event notification mechanism is being used
Aug 28 08:20:06 30.30.30.151 tac_plus-ng[668782]: child (pid 669689) terminated normally
Aug 28 08:24:02 30.30.30.151 tac_plus-ng[669826]: epoll event notification mechanism is being used
Aug 28 08:25:03 30.30.30.151 tac_plus-ng[668782]: child (pid 669826) terminated normally
Aug 28 08:29:01 30.30.30.151 tac_plus-ng[669964]: epoll event notification mechanism is being used
Aug 28 08:30:37 30.30.30.151 tac_plus-ng[668782]: child (pid 669964) terminated normally
....

I trie changе in
/etc/systemd/system/tac_plus-ng.service
[Service]
ExecStart=/usr/local/sbin/tac_plus-ng -f -d 4 /root/tac_plus-ng.cfg
No effect)

[MarcJHuber]

Hi,

you did redirect stdout, not stderr. "2>" is essential.

The scm_send_msg logs are normal, these just indicate that a worker process couldn't connect to the master.

Cheers,

Marc

[sea2space]

I understand.

When i run:
tac_plus-ng -d -4 -f tac_plus-ng.cfg 2> /dev/null

I don't see any system logs, empty

[MarcJHuber]

Hi,

sounds weird ... does "logger test" work?

Cheers,

Marc

[sea2space]

Yes, work

$logger test
$tail - /var/log/messages | grep test
$
$Sep 4 10:04:04 10.10.10.10 adminq[42520]: test

[MarcJHuber]

Hi,

I'm afraid I can't help you with this. Might be a local issue on your system, I've just validated on a secondary installation that debug logs are being sent to syslog if stderr isn't a tty.

Cheers,

Marc