Jump to content

mattenz

Members
 View Profile  See their activity

  • Posts

    18

  • Joined

  • Last visited

 Content Type 

Posts posted by mattenz

    Drives mounted as read-only after a while

    in General Support

    Posted · Edited by mattenz

    Okay, would that be: 

    btrfs scrub start -Bd /mnt/cache

     

    I get: 

    Scrub device /dev/sdh1 (id 1) done
Scrub started:    Mon Mar 20 09:50:37 2023
Status:           finished
Duration:         0:10:35
Total to scrub:   465.73GiB
Rate:             303.26MiB/s
Error summary:    csum=2
  Corrected:      0
  Uncorrectable:  2
  Unverified:     0

Scrub device /dev/sdi1 (id 3) done
Scrub started:    Mon Mar 20 09:50:37 2023
Status:           finished
Duration:         0:15:59
Total to scrub:   465.73GiB
Rate:             200.80MiB/s
Error summary:    super=3 verify=17451 csum=6709649
  Corrected:      6727098
  Uncorrectable:  2
  Unverified:     0
ERROR: there are uncorrectable errors

     

    Drives mounted as read-only after a while

    in General Support

    Posted · Edited by mattenz
    Removing diagnostics

    Hi all,

    I'm having an intermittent issue where my Docker containers will stop after a while due to trying to write to a read-only file. After restarting the array, fix common problems will flag that problem.

    Rebooting the server resolves the issue temporarily, but it will reoccur within a few days. As far as I can see, neither the array or cache are full. I'd appreciate some guidance on where to start tracking down this problem.

     

     

    [Support] Linuxserver.io - Snipe-it

    in Docker Containers

    Posted

    On 5/19/2021 at 6:31 AM, nikkita said:

     

    same here: needed to insert my ip+port from "APP_URL" manually behind the "server_name" to nginx/site-confs/default

    Thanks! I'm actually a bit of an idiot, so was getting upstream and downstream ports confused in nginx! Lesson learnt.

    [Support] Linuxserver.io - Snipe-it

    in Docker Containers

    Posted · Edited by mattenz

    13 hours ago, saarg said:

    Has that been reported to us before? The big you linked to is in the snipe-it repo and we don't follow issues there.

    Possibly not, I didn't mean to imply it was your bug (sorry). I had assumed that it a bug like that in the default repo that might be difficult to fix on your end.

    [Support] Linuxserver.io - Snipe-it

    in Docker Containers

    Posted · Edited by mattenz

    I'm getting some nginx error that prevents the webui from functioning. Frustratingly, the webui was working until I thought it might be a good idea to follow these steps, which I'm guessing are out of date (App key??)

      

    ErrorWarningSystemArrayLogin

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing...
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 10-adduser: executing...

-------------------------------------
_ ()
| | ___ _ __
| | / __| | | / \
| | \__ \ | | | () |
|_| |___/ |_| \__/


Brought to you by linuxserver.io
-------------------------------------

To support the app dev(s) visit:
Snipe-IT: https://snipeitapp.com/donate

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid: 99
User gid: 100
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 20-config: executing...
[cont-init.d] 20-config: exited 0.
[cont-init.d] 30-keygen: executing...
using keys found in /config/keys
[cont-init.d] 30-keygen: exited 0.
[cont-init.d] 40-config: executing...
[cont-init.d] 40-config: exited 0.
[cont-init.d] 99-custom-files: executing...
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-files: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
nginx: [emerg] invalid number of arguments in "server_name" directive in /config/nginx/site-confs/default:4
nginx: [emerg] invalid number of arguments in "server_name" directive in /config/nginx/site-confs/default:4
nginx: [emerg] invalid number of arguments in "server_name" directive in /config/nginx/site-confs/default:4
nginx: [emerg] invalid number of arguments in "server_name" directive in /config/nginx/site-confs/default:4
nginx: [emerg] invalid number of arguments in "server_name" directive in /config/nginx/site-confs/default:4
nginx: [emerg] invalid number of arguments in "server_name" directive in /config/nginx/site-confs/default:4
nginx: [emerg] invalid number of arguments in "server_name" directive in /config/nginx/site-confs/default:4
nginx: [emerg] invalid number of arguments in "server_name" directive in /config/nginx/site-confs/default:4
nginx: [emerg] invalid number of arguments in "server_name" directive in /config/nginx/site-confs/default:4
nginx: [emerg] invalid number of arguments in "server_name" directive in /config/nginx/site-confs/default:4

     

    And so on, looping on the nginx error.

     

    Edit: Fixed by adding APP_URL manually to nginx/site-confs/default. Not sure why that was required.

×
×
  • Create New...