[BUG] 197 errors in the logs since 20 July 2024, 12:23:17
Closed this issue · 4 comments
Is there an existing issue for this?
- I have searched the existing issues
Current Behavior
I get 197 errors in the logs since 20 July 2024, 12:23:17 show up when I do a scan. However, I cannot find where the errors are in the appdata logs folder or anywhere else
Expected Behavior
There should be some form of place of where the logs can be looked at or have some form of rotation so the logs can be cleared and thus remove the warning.
Steps To Reproduce
this issue is on unraid and shows up when once does a scan on the overview page
Environment
- OS: Unraid
- How docker service was installed: UnraidCPU architecture
x86-64
Docker creation
https://ibb.co/s3zq9jJContainer logs
text error warn system array login
0/0 [--->------------------------] 0% Starting ...
0/1 [>---------------------------] 0%
Starting ...
1/1 [============================] 100% Starting ...
0/1 [>---------------------------] 0%
Starting ...
1/1 [============================] 100% Starting ...
0/0 [------------->--------------] 0% Starting ...
0/1 [>---------------------------] 0%
Starting ...
1/1 [============================] 100% Starting ...
0/1 [>---------------------------] 0%
Starting ...
1/1 [============================] 100% Starting ...
0/0 [---------------------->-----] 0% Starting ...
0/1 [>---------------------------] 0%
Starting ...
1/1 [============================] 100% Starting ...
0/1 [>---------------------------] 0%
Starting ...
1/1 [============================] 100% Starting ...
0/0 [--->------------------------] 0% Starting ...
0/1 [>---------------------------] 0%
Starting ...
1/1 [============================] 100% Starting ...
0/1 [>---------------------------] 0%
Starting ...
1/1 [============================] 100% Starting ...
0/0 [------------->--------------] 0% Starting ...
0/1 [>---------------------------] 0%
Starting ...
1/1 [============================] 100%nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/site-confs/default.conf:13
nginx: [warn] the "listen ... http2" directive is deprecated, use the "http2" directive instead in /config/nginx/site-confs/default.conf:14
Update app notes from App Store
Restore default tags that are missing
Purify and migrate collected mail addresses
Insert background jobs for all accounts
Update app spreed from App Store
Restore default tags that are missing
Purify and migrate collected mail addresses
Insert background jobs for all accounts
Restore default tags that are missing
Purify and migrate collected mail addresses
Insert background jobs for all accounts
Restore default tags that are missing
Purify and migrate collected mail addresses
Insert background jobs for all accounts
Starting code integrity check...
Finished code integrity check
Update successful
Turned off maintenance mode
Resetting log level
Initializing finished
**** The following active confs have different version dates than the samples that are shipped. ****
**** This may be due to user customization or an update to the samples. ****
**** You should compare the following files to the samples in the same folder and update them. ****
**** Use the link at the top of the file to view the changelog. ****
┌────────────┬────────────┬────────────────────────────────────────────────────────────────────────┐
│ old date │ new date │ path │
├────────────┼────────────┼────────────────────────────────────────────────────────────────────────┤
│ 2023-04-13 │ 2024-05-27 │ /config/nginx/nginx.conf │
│ 2023-06-23 │ 2024-06-24 │ /config/nginx/site-confs/default.conf │
└────────────┴────────────┴────────────────────────────────────────────────────────────────────────┘
[custom-init] No custom files found, skipping...
[ls.io-init] done.Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
this is not a container issue, nextcloud offers their own support.
that said, your container logs are telling you to do some certain tasks, i do suggest doing them.
closing as out of scope.
(also the logs are in the bind paths our container readme says to use, you are able to just delete them if you wish. logrotate is handled by nextcloud and covered in their documentation)
This issue is locked due to inactivity