Jump to content

soana

Members
  • Posts

    242
  • Joined

  • Last visited

Posts posted by soana

  1. For some reason my quad Intel NIC does not have wol_magic enabeled by default.

    After fighting with the /etc/rc.conf.local or /usr/local/etc/rc.d script not executing at boot I figured out that in order to enable wol_magic on a quad intel nic on my hardware pfsense box I had to add the following to the Services->Shellcmd->Command: ifconfig igb1 wol_magic (replace igb1 with the NIC interface that you want to use to wake up the hardware pfsense box - hint it should be the LAN one) , Shellcmd Type: shellcmd

    Shellcmd is a package that can be installed using the Package Manager - compared with the /etc/rc.conf.local method this way the command is saved in the config.xml file for backup/restore purposes.

     

     

     

     

  2. If you are sure that the parity is OK you could do that.

     

    Much safer would be to:

    1. make a note of the parity drive  or better off just disconnect the parity drive

    2. go to Tools-> new config -> apply

    3. go back to Main tab and add the two drives as disk1 and disk2

    4. start the array

     

    If everything is OK and you can access all the data stop the machine and add the parity drive - no parity rebuild is reqired, if not then you might have mixed up the data with the parity drive.

     

  3. Please ignore my initial message or learn from this ....

    Error message below is for linuxserver unifi container (linuxserver/unifi:unstable) and not the linuxserve unifi-controller container (linuxserver/unifi-controller:latest).

     

    Migrating from unifi docker to unifi-controller docker was easy:

    1. within the old controller Settings->Maintenance->Download backup

    2. shutdown linuxserver/unifi:unstable

    3. install the linuxserver/unifi-controller:5.9

    4. after launching the new container restore from backup

    5. stop container and change from linuxserver/unifi-controller:5.9 to linuxserver/unifi-controller:latest

    6. done + facepalm!

    -------------------------------------------------------------------------------------------

    Swiched from unstable to latest with error message:

    "We do not support upgrading from 5.9.29."

     

     

    Screen Shot 2019-02-23 at 4.00.50 PM.png

  4. On 8/21/2018 at 11:29 AM, jude said:

    Thanks for the great tutorial and for all of the others you make. They really make it easy to get the most out of our unRaid boxes.

     

    I have a question regarding an error that I am getting when trying to back up photos/videos from my daughters iPhone to my server using NextCloud. Everything works well except for larger video files which wont upload and give a 413 error (request entity too large). I did some Googling and found this page  https://github.com/nextcloud/docker/issues/261 which has a final post by @bhansley stating;

     

    "For anyone else who run across this issue, in addition to setting upload size in the Nextcloud UI, I had to tweak my upstream Nginx proxy to allow bigger uploads."

    
    client_max_body_size        10G;
    client_body_buffer_size     400M;

     

    Could someone direct me to where this upstream Nginx proxy config setting should go?

     

    Same issue here.

    The client_max_body_size is located in the  /appdata/letsencrypt/nginx/nginx.conf file but the value is set to zero that means no size limit.

    I did set the value to 10G and the same in the nexcloud GUI but still getting the 413 error.

     

    More info

  5. After a reboot today of the server I got the message above.

    Cache drive seems to be only half full based on the report on the Main tab.

    Error message:

    Nov 28 17:54:51 Tower kernel: BTRFS error (device sdg1): parent transid verify failed on 495321088 wanted 1852238 found 1852237
    Nov 28 17:54:51 Tower kernel: BTRFS: error (device sdg1) in __btrfs_free_extent:6989: errno=-5 IO failure
    Nov 28 17:54:51 Tower kernel: BTRFS info (device sdg1): forced readonly
    Nov 28 17:54:51 Tower kernel: BTRFS: error (device sdg1) in btrfs_run_delayed_refs:3009: errno=-5 IO failure
    Nov 28 17:54:51 Tower shfs: error: shfs_rename: Read-only file system (30): rename: /mnt/cache/appdata/plex/Library/Application Support/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.agents.subzero.log.4 /mnt/cache/appdata/plex/Library/Application Support/Plex Media Server/Logs/PMS Plugin Logs/com.plexapp.agents.subzero.log.5
    Nov 28 17:54:51 Tower kernel: BTRFS error (device sdg1): pending csums is 217088

    Making a copy of the cache drive right now and will try next:

    1. reset the cache drive cables

    2. reformat the cache drive if above fails.

    tower-diagnostics-20171128-1822.zip

  6. On 8/25/2017 at 1:16 AM, Wob76 said:

    Going to add another request :)

     

    At the moment the custom icon uploading doesn't work, there is permission issues with 2 folders

    /tmp and /var/lib/domoticz/www/images

    I did a chmod 777 to both and the upload starts to work.

     

    But even with it working, the new icons will not survive a docker update and the www/images folder is inside the container. Maybe moving the whole image folder into /config, that would fix the custom icons and floorplans.

     

    Thanks,

    Wob

    +1 on Wob76 request; would love to have www in the config folder.

  7. On 6/30/2017 at 6:29 AM, kazoodude said:

    I found this one today but haven't figured out how to get it working in UNRAID.

    Perhaps some more experienced users might be able to chime in and help out.
    https://hub.docker.com/r/kmcgill88/k-plex/

     

    Here is a way to do it assuming you already have linuxserver container running on your server:

    1. go to: \\Tower\flash\config\plugins\dockerMan\templates-user

    2. copy my-plex.xml to my-k-plex.xml

    3. edit the new xml file and change line tree and four per below and save

      <Name>k-plex</Name>
      <Repository>kmcgill88/k-plex</Repository>

    4. Stop your current linuxserver docker container and add a new container using the k-plex template that you just created.

    5. After the container is running follow the instructions from https://hub.docker.com/r/kmcgill88/k-plex/

    6. Done.

     

    Enjoy and send your thanks to linuxserver, kmcgill88 and erikkaashoek.

     

    • Upvote 2
  8. Could not find a better pattern yet but my server tends to freeze overnight on random days.

    The issue occurred several times over the last couple of weeks usually overnight, in the morning I would find the server unresponsive over web and sometimes over ssh also.

    When it first happened I was able to ssh into the tower but the command line diagnostics  failed and the system froze and the only way back was a reset, no diagnostics file was created.

    Second time the system just plainly froze both web access and ssh.

    Third time was last night at this time server web page was not responding but I was able to get the diagnostics zip file trough ssh but powerdown -r did not work so eventually I had to push the reset button again.

    Attached is the diagnostics file, I looked trough it but could not find anything out of the ordinary.

    tower-diagnostics-20170605-1706.zip

  9. Started to get this message from FCP plugin.

    Diagnostics file attached.

    As it turns out it seems that the CPU temp is going over the threshold, did check the CPU fan and it's working OK.

    Also the time the temp is going over and comes back to normal is the same:

    Apr 21 22:57:57 Tower kernel: CPU1: Core temperature above threshold, cpu clock throttled (total events = 63966)
    Apr 21 22:57:57 Tower kernel: CPU5: Core temperature above threshold, cpu clock throttled (total events = 63966)
    Apr 21 22:57:57 Tower kernel: CPU7: Package temperature above threshold, cpu clock throttled (total events = 90142)
    Apr 21 22:57:57 Tower kernel: CPU6: Package temperature above threshold, cpu clock throttled (total events = 90142)
    Apr 21 22:57:57 Tower kernel: CPU2: Package temperature above threshold, cpu clock throttled (total events = 90142)
    Apr 21 22:57:57 Tower kernel: CPU3: Package temperature above threshold, cpu clock throttled (total events = 90142)
    Apr 21 22:57:57 Tower kernel: CPU5: Package temperature above threshold, cpu clock throttled (total events = 90138)
    Apr 21 22:57:57 Tower kernel: CPU0: Package temperature above threshold, cpu clock throttled (total events = 90142)
    Apr 21 22:57:57 Tower kernel: CPU4: Package temperature above threshold, cpu clock throttled (total events = 90142)
    Apr 21 22:57:57 Tower kernel: mce_notify_irq: 1 callbacks suppressed
    Apr 21 22:57:57 Tower kernel: mce: [Hardware Error]: Machine check events logged
    Apr 21 22:57:57 Tower kernel: CPU5: Core temperature/speed normal
    Apr 21 22:57:57 Tower kernel: CPU6: Package temperature/speed normal
    Apr 21 22:57:57 Tower kernel: CPU0: Package temperature/speed normal
    Apr 21 22:57:57 Tower kernel: CPU7: Package temperature/speed normal
    Apr 21 22:57:57 Tower kernel: CPU2: Package temperature/speed normal
    Apr 21 22:57:57 Tower kernel: CPU4: Package temperature/speed normal
    Apr 21 22:57:57 Tower kernel: CPU3: Package temperature/speed normal
    Apr 21 22:57:57 Tower kernel: CPU5: Package temperature/speed normal
    Apr 21 22:57:57 Tower kernel: mce: [Hardware Error]: Machine check events logged

    Is this a false positive or is it something different?

    tower-diagnostics-20170423-0726.zip

×
×
  • Create New...