Jump to content

joggs

Members
 View Profile  See their activity

  • Posts

    36

  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

joggs's Achievements

Noob

Noob (1/14)

9

Reputation

  1. joggs
    nano /boot/config/smb-extra.conf samba restart
  2. joggs
    I see that this app hasn't been updated for 5 months, while the original cloudflare docker was updated 4 days ago, so maybe that is the reason. I am running the original cloudflare/cloudflared:latest docker and that works well
  3. joggs
    Same here. I think this was the same error we had a year ago or so, where the gui also starts to fail. The docker page does not load properly, and the cpu stats etc on the dashbord also fails The temporary fix was to do /etc/rc.d/rc.nginx restart /etc/rc.d/rc.nginx reload but it was then fixed.
  4. joggs
    Ouch, The dreaded death of the nginx process is back in .12.11 The gui has started to die on me each day since .12.11 This was fixed a year ago or so, but it seems to be back. /etc/rc.d/rc.nginx restart /etc/rc.d/rc.nginx reload Fixes it temporarily I've had a stable system for months, until the upgrade, which then has has situations like these: Syslog : Jul 21 10:30:15 Tower nginx: 2024/07/21 10:30:15 [error] 22241#22241: *561672 nchan: error publishing message (HTTP status code 507), client: unix:, server: , req uest: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost" Jul 21 10:30:15 Tower kernel: nginx[22241]: segfault at 0 ip 0000000000000000 sp 00007fffc6604028 error 14 in nginx[400000+24000] likely on CPU 10 (core 2, socket 0) Jul 21 10:30:15 Tower kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Jul 21 10:30:15 Tower nginx: 2024/07/21 10:30:15 [alert] 4280#4280: worker process 22241 exited on signal 11 Jul 21 10:30:15 Tower nginx: 2024/07/21 10:30:15 [crit] 22786#22786: ngx_slab_alloc() failed: no memory Jul 21 10:30:15 Tower nginx: 2024/07/21 10:30:15 [error] 22786#22786: shpool alloc failed Jul 21 10:30:15 Tower nginx: 2024/07/21 10:30:15 [error] 22786#22786: nchan: Out of shared memory while allocating channel m/ Jul 21 10:30:15 Tower nginx: 2024/07/21 10:30:15 [alert] 22786#22786: *561673 header already sent while keepalive, client: 172.18.0.19, server: 192.168.0.40:80 Jul 21 10:30:15 Tower nginx: 2024/07/21 10:30:15 [crit] 22786#22786: ngx_slab_alloc() failed: no memory Jul 21 10:30:15 Tower nginx: 2024/07/21 10:30:15 [error] 22786#22786: shpool alloc failed Jul 21 10:30:15 Tower nginx: 2024/07/21 10:30:15 [error] 22786#22786: nchan: Out of shared memory while allocating channel /disks. Increase nchan_max_reserved_mem ory. Jul 21 10:30:15 Tower nginx: 2024/07/21 10:30:15 [error] 22786#22786: *561675 nchan: error publishing message (HTTP status code 507), client: unix:, server: , req uest: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Jul 21 10:30:15 Tower kernel: nginx[22786]: segfault at 0 ip 0000000000000000 sp 00007fffc6604028 error 14 in nginx[400000+24000] likely on CPU 0 (core 0, socket 0) Jul 21 10:30:15 Tower kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Jul 21 10:30:15 Tower nginx: 2024/07/21 10:30:15 [alert] 4280#4280: worker process 22786 exited on signal 11 Jul 21 10:30:15 Tower nginx: 2024/07/21 10:30:15 [crit] 22862#22862: ngx_slab_alloc() failed: no memory Jul 21 10:30:15 Tower nginx: 2024/07/21 10:30:15 [error] 22862#22862: shpool alloc failed Jul 21 10:30:15 Tower nginx: 2024/07/21 10:30:15 [error] 22862#22862: nchan: Out of shared memory while allocating channel m/ Jul 21 10:30:15 Tower nginx: 2024/07/21 10:30:15 [alert] 22862#22862: *561676 header already sent while keepalive, client: 172.18.0.19, server: 192.168.0.40:80 Jul 21 10:30:16 Tower kernel: nginx[22862]: segfault at 0 ip 0000000000000000 sp 00007fffc6604028 error 14 in nginx[400000+24000] likely on CPU 2 (core 2, socket 0) Jul 21 10:30:16 Tower kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Jul 21 10:30:16 Tower nginx: 2024/07/21 10:30:16 [alert] 4280#4280: worker process 22862 exited on signal 11 Jul 21 10:30:16 Tower nginx: 2024/07/21 10:30:16 [crit] 23014#23014: ngx_slab_alloc() failed: no memory Jul 21 10:30:16 Tower nginx: 2024/07/21 10:30:16 [error] 23014#23014: shpool alloc failed Jul 21 10:30:16 Tower nginx: 2024/07/21 10:30:16 [error] 23014#23014: nchan: Out of shared memory while allocating channel /dockerload. Increase nchan_max_reserve d_memory. Jul 21 10:30:16 Tower nginx: 2024/07/21 10:30:16 [alert] 23014#23014: *561681 header already sent while keepalive, client: 172.18.0.19, server: 192.168.0.40:80 Jul 21 10:30:16 Tower unraid-api[7247]: 👋 Farewell. UNRAID API shutting down! Jul 21 10:30:16 Tower nginx: 2024/07/21 10:30:16 [crit] 23014#23014: ngx_slab_alloc() failed: no memory Jul 21 10:30:16 Tower nginx: 2024/07/21 10:30:16 [error] 23014#23014: shpool alloc failed Jul 21 10:30:16 Tower nginx: 2024/07/21 10:30:16 [error] 23014#23014: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_m emory. Jul 21 10:30:16 Tower nginx: 2024/07/21 10:30:16 [error] 23014#23014: *561683 nchan: error publishing message (HTTP status code 507), client: unix:, server: , req uest: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost" Jul 21 10:30:16 Tower nginx: 2024/07/21 10:30:16 [crit] 23014#23014: ngx_slab_alloc() failed: no memory Jul 21 10:30:16 Tower nginx: 2024/07/21 10:30:16 [error] 23014#23014: shpool alloc failed Jul 21 10:30:16 Tower nginx: 2024/07/21 10:30:16 [error] 23014#23014: nchan: Out of shared memory while allocating channel /disks. Increase nchan_max_reserved_mem ory. Jul 21 10:30:16 Tower nginx: 2024/07/21 10:30:16 [error] 23014#23014: *561684 nchan: error publishing message (HTTP status code 507), client: unix:, server: , req uest: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Jul 21 10:30:17 Tower nginx: 2024/07/21 10:30:17 [crit] 23014#23014: ngx_slab_alloc() failed: no memory Jul 21 10:30:17 Tower nginx: 2024/07/21 10:30:17 [error] 23014#23014: shpool alloc failed Jul 21 10:30:17 Tower nginx: 2024/07/21 10:30:17 [error] 23014#23014: nchan: Out of shared memory while allocating channel /cpuload. Increase nchan_max_reserved_m emory. Jul 21 10:30:17 Tower nginx: 2024/07/21 10:30:17 [error] 23014#23014: *561688 nchan: error publishing message (HTTP status code 507), client: unix:, server: , req uest: "POST /pub/cpuload?buffer_length=1 HTTP/1.1", host: "localhost" Jul 21 10:30:17 Tower kernel: nginx[23014]: segfault at 0 ip 0000000000000000 sp 00007fffc6604028 error 14 in nginx[400000+24000] likely on CPU 12 (core 4, socket 0) Jul 21 10:30:17 Tower kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Jul 21 10:30:17 Tower nginx: 2024/07/21 10:30:17 [alert] 4280#4280: worker process 23014 exited on signal 11 Jul 21 10:30:17 Tower nginx: 2024/07/21 10:30:17 [crit] 23165#23165: ngx_slab_alloc() failed: no memory Jul 21 10:30:17 Tower nginx: 2024/07/21 10:30:17 [error] 23165#23165: shpool alloc failed Jul 21 10:30:17 Tower nginx: 2024/07/21 10:30:17 [error] 23165#23165: nchan: Out of shared memory while allocating channel m/ Jul 21 10:30:17 Tower nginx: 2024/07/21 10:30:17 [alert] 23165#23165: *561689 header already sent while keepalive, client: 172.18.0.19, server: 192.168.0.40:80 Jul 21 10:30:17 Tower kernel: nginx[23165]: segfault at 0 ip 0000000000000000 sp 00007fffc6604028 error 14 in nginx[400000+24000] likely on CPU 14 (core 6, socket 0) Jul 21 10:30:17 Tower kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Jul 21 10:30:17 Tower nginx: 2024/07/21 10:30:17 [alert] 4280#4280: worker process 23165 exited on signal 11 Jul 21 10:30:17 Tower nginx: 2024/07/21 10:30:17 [crit] 23170#23170: ngx_slab_alloc() failed: no memory Jul 21 10:30:17 Tower nginx: 2024/07/21 10:30:17 [error] 23170#23170: shpool alloc failed Jul 21 10:30:17 Tower nginx: 2024/07/21 10:30:17 [error] 23170#23170: nchan: Out of shared memory while allocating channel /dockerload. Increase nchan_max_reserve d_memory. Jul 21 10:30:17 Tower nginx: 2024/07/21 10:30:17 [alert] 23170#23170: *561691 header already sent while keepalive, client: 172.18.0.19, server: 192.168.0.40:80 Jul 21 10:30:17 Tower nginx: 2024/07/21 10:30:17 [crit] 23170#23170: ngx_slab_alloc() failed: no memory Jul 21 10:30:17 Tower nginx: 2024/07/21 10:30:17 [error] 23170#23170: shpool alloc failed Jul 21 10:30:17 Tower nginx: 2024/07/21 10:30:17 [error] 23170#23170: nchan: Out of shared memory while allocating channel /disks. Increase nchan_max_reserved_mem ory. Jul 21 10:30:17 Tower nginx: 2024/07/21 10:30:17 [error] 23170#23170: *561693 nchan: error publishing message (HTTP status code 507), client: unix:, server: , req uest: "POST /pub/disks?buffer_length=1 HTTP/1.1", host: "localhost" Jul 21 10:30:17 Tower kernel: nginx[23170]: segfault at 0 ip 0000000000000000 sp 00007fffc6604028 error 14 in nginx[400000+24000] likely on CPU 15 (core 7, socket 0) Jul 21 10:30:17 Tower kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Jul 21 10:30:18 Tower nginx: 2024/07/21 10:30:18 [alert] 4280#4280: worker process 23170 exited on signal 11 Jul 21 10:30:18 Tower nginx: 2024/07/21 10:30:18 [crit] 23196#23196: ngx_slab_alloc() failed: no memory Jul 21 10:30:18 Tower nginx: 2024/07/21 10:30:18 [error] 23196#23196: shpool alloc failed Jul 21 10:30:18 Tower nginx: 2024/07/21 10:30:18 [error] 23196#23196: nchan: Out of shared memory while allocating channel m/ Jul 21 10:30:18 Tower nginx: 2024/07/21 10:30:18 [alert] 23196#23196: *561694 header already sent while keepalive, client: 172.18.0.19, server: 192.168.0.40:80 Jul 21 10:30:18 Tower kernel: nginx[23196]: segfault at 4b1 ip 0000000000469244 sp 00007fffc6604090 error 6 in nginx[424000+110000] likely on CPU 0 (core 0, socke t 0) Jul 21 10:30:18 Tower kernel: Code: 50 30 48 89 df 5b e9 1b ee ff ff 0f 1f 00 ff 50 38 48 89 df 5b e9 0c ee ff ff 0f 1f 40 00 48 8b 90 e8 03 00 00 48 89 c7 31 f6 83 82 90 04 00 00 01 e8 8f fe ff ff 48 89 df 5b e9 e6 ed ff ff Jul 21 10:30:18 Tower nginx: 2024/07/21 10:30:18 [alert] 4280#4280: worker process 23196 exited on signal 11 Jul 21 10:30:22 Tower nginx: 2024/07/21 10:30:22 [alert] 23566#23566: worker process 23819 exited on signal 6 Jul 21 10:30:26 Tower root: {"level":"info","time":"2024-07-21T08:30:25.800Z","pid":23572,"hostname":"Tower","logger":"cli","msg":"Starting [email protected]"} Jul 21 10:30:26 Tower root: {"level":"info","time":"2024-07-21T08:30:26.099Z","pid":23572,"hostname":"Tower","msg":"Watch Setup on Config Path: /boot/config/plugins/dynamix.my.servers/myservers.cfg"} Jul 21 10:30:28 Tower nginx: 2024/07/21 10:30:28 [alert] 23566#23566: worker process 25177 exited on signal 6 Jul 21 10:30:30 Tower nginx: 2024/07/21 10:30:30 [alert] 23566#23566: worker process 27195 exited on signal 6 Jul 21 10:30:30 Tower nginx: 2024/07/21 10:30:30 [alert] 23566#23566: worker process 28163 exited on signal 6 Jul 21 10:30:32 Tower nginx: 2024/07/21 10:30:32 [alert] 23566#23566: worker process 28336 exited on signal 6 Jul 21 10:30:32 Tower nginx: 2024/07/21 10:30:32 [alert] 23566#23566: worker process 29049 exited on signal 6 Jul 21 10:30:32 Tower unraid-api[26606]: ✔️ UNRAID API started successfully! Jul 21 10:30:34 Tower nginx: 2024/07/21 10:30:34 [alert] 23566#23566: worker process 29145 exited on signal 6 Jul 21 10:30:34 Tower nginx: 2024/07/21 10:30:34 [alert] 23566#23566: worker process 29225 exited on signal 6 Jul 21 10:30:36 Tower nginx: 2024/07/21 10:30:36 [alert] 23566#23566: worker process 29231 exited on signal 6 Jul 21 10:30:38 Tower nginx: 2024/07/21 10:30:38 [alert] 23566#23566: worker process 29430 exited on signal 6 Jul 21 10:30:38 Tower nginx: 2024/07/21 10:30:38 [alert] 23566#23566: worker process 29499 exited on signal 6 Jul 21 10:30:40 Tower nginx: 2024/07/21 10:30:40 [alert] 23566#23566: worker process 29508 exited on signal 6 Jul 21 10:30:42 Tower nginx: 2024/07/21 10:30:42 [alert] 23566#23566: worker process 29949 exited on signal 6 Jul 21 10:30:44 Tower nginx: 2024/07/21 10:30:44 [alert] 23566#23566: worker process 30105 exited on signal 6 Jul 21 10:30:46 Tower nginx: 2024/07/21 10:30:46 [alert] 23566#23566: worker process 30165 exited on signal 6 Jul 21 10:30:46 Tower nginx: 2024/07/21 10:30:46 [alert] 23566#23566: worker process 30294 exited on signal 6 Jul 21 10:30:48 Tower nginx: 2024/07/21 10:30:48 [alert] 23566#23566: worker process 30303 exited on signal 6 Jul 21 10:30:48 Tower nginx: 2024/07/21 10:30:48 [alert] 23566#23566: worker process 30382 exited on signal 6 Jul 21 10:30:50 Tower nginx: 2024/07/21 10:30:50 [alert] 23566#23566: worker process 30391 exited on signal 6 Jul 21 10:30:50 Tower nginx: 2024/07/21 10:30:50 [alert] 23566#23566: worker process 30709 exited on signal 6 Jul 21 10:30:52 Tower nginx: 2024/07/21 10:30:52 [alert] 23566#23566: worker process 30718 exited on signal 6 Jul 21 10:30:52 Tower nginx: 2024/07/21 10:30:52 [alert] 23566#23566: worker process 30835 exited on signal 6 Jul 21 10:30:54 Tower nginx: 2024/07/21 10:30:54 [alert] 23566#23566: worker process 30851 exited on signal 6 Jul 21 10:30:54 Tower nginx: 2024/07/21 10:30:54 [alert] 23566#23566: worker process 30924 exited on signal 6 Jul 21 10:30:56 Tower nginx: 2024/07/21 10:30:56 [alert] 23566#23566: worker process 30930 exited on signal 6 Jul 21 10:30:56 Tower nginx: 2024/07/21 10:30:56 [alert] 23566#23566: worker process 31083 exited on signal 6 Jul 21 10:30:58 Tower nginx: 2024/07/21 10:30:58 [alert] 23566#23566: worker process 31092 exited on signal 6 Jul 21 10:30:58 Tower nginx: 2024/07/21 10:30:58 [alert] 23566#23566: worker process 31155 exited on signal 6 Jul 21 10:31:00 Tower nginx: 2024/07/21 10:31:00 [alert] 23566#23566: worker process 31164 exited on signal 6 Jul 21 10:31:00 Tower nginx: 2024/07/21 10:31:00 [alert] 23566#23566: worker process 31343 exited on signal 6 Jul 21 10:31:02 Tower nginx: 2024/07/21 10:31:02 [alert] 23566#23566: worker process 31479 exited on signal 6 Jul 21 10:31:02 Tower nginx: 2024/07/21 10:31:02 [alert] 23566#23566: worker process 31565 exited on signal 6 Jul 21 10:31:04 Tower nginx: 2024/07/21 10:31:04 [alert] 23566#23566: worker process 31611 exited on signal 6
  5. joggs
    there seems to be permission problems installing in from scratch /usr/src/app/redisinsight/api/node_modules/file-stream-rotator/lib/helper.js:16 throw error; ^ Error: EACCES: permission denied, mkdir '/data/logs' at Object.mkdirSync (node:fs:1398:3) at makeDirectory (/usr/src/app/redisinsight/api/node_modules/file-stream-rotator/lib/helper.js:12:12) at FileStreamRotator.createNewLog (/usr/src/app/redisinsight/api/node_modules/file-stream-rotator/lib/FileStreamRotator.js:140:36) at FileStreamRotator.rotate (/usr/src/app/redisinsight/api/node_modules/file-stream-rotator/lib/FileStreamRotator.js:133:14) at new FileStreamRotator (/usr/src/app/redisinsight/api/node_modules/file-stream-rotator/lib/FileStreamRotator.js:22:14) at Object.getStream (/usr/src/app/redisinsight/api/node_modules/file-stream-rotator/lib/index.js:32:12) at new DailyRotateFile (/usr/src/app/redisinsight/api/node_modules/winston-daily-rotate-file/daily-rotate-file.js:80:57) at Object.<anonymous> (/usr/src/app/redisinsight/api/dist/config/logger.js:18:27) at Module._compile (node:internal/modules/cjs/loader:1256:14) at Module._extensions..js (node:internal/modules/cjs/loader:1310:10) { errno: -13, syscall: 'mkdir', code: 'EACCES', path: '/data/logs' chmodding it makes no difference and chown'ing it gives other errors. What fixed it for me was adding some variables: PUID:99 PGID:100 UMASK:000
  6. joggs
    Thanks for this! Force update the container shrunk the container size from 5GB to 300MB. It must be a log file or something that should be mapped to the appdata dir instead of inside the container.
  7. joggs
    Same problems here. 100% zfs usage and nothing in syslogserver about the crash. This started happening a couple of days after converting my nvme cache that stores vm's and dockers to zfs. I'm dedicating 64GB of my 128GB to ZFS but the total ram usage was around 80% when crashing
  8. joggs
    Dynamix are the culprits. Either dynamix.system.temp.plg or dynamix.unraid.net.plg is the problem.
  9. joggs
    This happens from time to time with unraid. It usually is caused by a plugin, so you have to remove them one by one and see which one that causes the problem. I also have this problem rigt now, and it looks like 4 plugins has een updated recently, so I'll try to find which one it is. Unraid should be able to handle this in a better way, as you will waste a day or two each time
  10. joggs
    Is copy/paste from outside obisidian into obsidian supposed to be working? It does not for me. I suppose based on the fact that it runs in xterm? The way I would use obsidian is to paste content into it in 99% of my use cases.
  11. joggs
    Well, what you are saying is what the instruction should say Snualfy. You are filling in alot of blanks based on your experience.
  12. joggs
    I'll wait another couple of weeks. When I was upgrading from 11.2 to 11.3 i couldn't roll back as unraid halted at boot with the same error as I got after the upgrade, even after a full restore, so that is not always a 100% safety net. Lets create a "real stable" branch which is auto generated each time we reach the x.y.10 version! I
  13. joggs
    If I remove all plugins, unraid boots, so it seems likely a plugin is the problem.
  14. joggs
    yes. I have not removed the nerd tools or what they are called though, the one that still not are compatible with 6.11
  15. joggs
    removing unassigned devices directory and the file unassigned.devices.plg did not help, if that was how you meant. Still stuck on starting samba
×
×
  • Create New...