Made a mess, need help untangling - /etc/rsyslog.conf got deleted and now have issues

Server
1

OK - I was doing something on my server and kept getting distracted
I know I should have walked away and come back to it…hindsight

I was trying to get rsync working on another box (a nas) and I used autocomplete or something
I was attempting to delete /etc/rsyncd.conf
I managed to delete /etc/rsyslog.conf

Of course I did not notice till a day or so later
Luckily I had an old version of rsyslog.conf (but possibly 2 years older)
I replaced the file, I thought I had saved a massive headache…but it appears it is not that straight forward

I am not getting any logging to /var/log/owncloud.log

Stuff I have tried
changing log level to 0 (debugging)
I have restarted apache
I have manually done a logrotate

I can see that stuff is getting logged in /etc/apache2/access.log
Owncloud is seemingly all working, just not logging to /var/log/owncloud.log

I am unsure what (if any) changes owncloud makes to the /etc/syslog.conf, or even if it is unrelated - or a direct consequence and importantly - how I get it working again!

Running Debian 10
ownCloud 10.13.3 (stable)
I would update, but holding off incase I further break something else

Have backed up all personal files (only 3 users)…just in case I have really messed stuff up
Wishing I had backed up /etc before diving in there going sudo gung-ho!

Any help appreciated!

2

Interestingly - when I go to the admin page on the server and go into settings - I can download the log - and it seems to be right
(set log level to 0 it gives everything and more - date and timestamps are current - so is not an old log)
So it IS logging…just not where I expect it would be in /var/log/owncloud.log
(unless I am misunderstanding what is going on here)

I manually removed /var/log/owncloud.log in the hopes that logrotate would create a new one …but it hasn’t

3

Can be closed :smiley:

Not entirely sure what I did that actually “fixed it”
Played with the owncloud monthly cron (ran it a few times), started and stopped the syslog, touched the “/var/log/owncloud.log” shouted at the screen, had a brew, calmed down and then noticed the terminal that /was/ showing nothing with a tail -f /var/log/owncloud was actually whirring away with data

Maybe it was just “calmly having a cup of tea” that was missing…who knows…

Possibly disaster averted for now
lesson learned - don’t use the terminal with root permissions whilst stuff if going on around me - back up that file …before doing anything

4

Hey,

i think this is unrelated and ownCloud doesn’t make any changes to such system wide configuration files.