Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Since the inclusion of "easylogging", loggedfs does not log ANYTHING #15

Closed
s-m-e opened this issue Apr 11, 2019 · 2 comments · Fixed by #23
Closed

Since the inclusion of "easylogging", loggedfs does not log ANYTHING #15

s-m-e opened this issue Apr 11, 2019 · 2 comments · Fixed by #23

Comments

@s-m-e
Copy link

s-m-e commented Apr 11, 2019

With commit 02339be and earlier, things work as expected. With commit 6a85fbd and later (with the inclusion of easylogging, loggedfs essentially does not log anything for me anymore - even if I allow everything in the XML configuration file.

All I get is something along those lines ...

2019-04-11 12:42:10,442 INFO [default] Configuration file : /demo/test_loggedfs_cfg.xml
2019-04-11 12:42:10,442 INFO [default] LoggedFS running as a public filesystem
2019-04-11 12:42:10,442 INFO [default] LoggedFS starting at /demo/test_mount/test_child.
2019-04-11 12:42:10,442 INFO [default] Using configuration file /demo/test_loggedfs_cfg.xml.
2019-04-11 12:42:10,442 INFO [default] chdir to /demo/test_mount/test_child
2019-04-11 12:42:10,755 INFO [default] LoggedFS closing.

... although I ran a few actions on it, like creating a file, changing it, etc.


Testing on openSUSE Leap 42.3 x86_64, patch level as of today. Tried to compile with both g++ 4.7 and 6.2.

@s-m-e
Copy link
Author

s-m-e commented Apr 11, 2019

Narrowed it down. It is this little blob, which is causing this annoyance:

        if (loggedfsArgs->isDaemon)
        {
            dispatchAction = el::base::DispatchAction::SysLog;
            loggerId = "syslog";
        }

If in daemon mode, logged data (at least in my case) ONLY goes to the sys log. Except loggedfs status information, which goes to the log file itself (as expected).

Workaround, if you do not need the sys log: Comment the above 5 lines.

@teeks99
Copy link

teeks99 commented Nov 20, 2021

I also have this problem.

I believe running the following should provide better output:

root@8e36fd945083:~# mkdir /tmp/TEST
root@8e36fd945083:~# loggedfs -l log.txt /tmp/TEST
2021-11-20 08:25:50,401 INFO [default] LoggedFS log file : log.txt
root@8e36fd945083:~# echo this is some data > /tmp/TEST/test.txt
root@8e36fd945083:~# cat log.txt 
2021-11-20 08:25:50,402 INFO [default] LoggedFS starting at /tmp/TEST.
2021-11-20 08:25:50,402 INFO [default] chdir to /tmp/TEST
root@8e36fd945083:~# 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants