NewDisplayName

Members
  • Posts

    2288
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by NewDisplayName

  1. does this still work? Seems so, but "api" doenst start automatic, i hat to use /opt/pynab# python3 pynab.py api pynab:api: started to be able to add it to nzbhydra. I bought nn+ and added it, its currently backfilling, but doenst show anything under stats (the webpage), prebot doenst seem to work (only reconnecting with new rnd names)... but for what is that used? Can it work without prebot? if we should/could/must buy nn+ why not use their client as docker? Anyway, in logs update i find many releases, but when i search for them, tehy dont appear, do i need to do anything else? How does he know what category rls are? (bc in webpage i have to specifiy rls categories) edit: nvm, just took longer then i expected to show anything, categories works and a quite a few things got added tried to disable tvrage and nfo, but then docker crashes , not expected false u cant add new groups, or delete old, they get just readded after restart.... (i tried via cmd line and via the groups.json) was really a pain, but not working. It doenst use that file, but created it..? Oo besides this it seems to work very fast and easy.
  2. ehhhhhh... dont need to use user script for mover, just install CA mover plugin
  3. Thats the problem, i was not able to produce a usefull syslog (i tried tail -f to user share) But there is nothing "crashing" in it. I guess it must be more then just connectifity error then, because /mnt/user/something is only in ram, and if there is nothing logged, then it must be a bigger problem then just network. problem is i have currently a parity rebuild running, it says it need 5 days.. so i guess well have to wait for a next try. btw while the crash i plugged in VGA, and it just said normal: "blabla your server is reachable under ... Login:"
  4. Good, just want to make sure, bc i thought ram would be /tmp is /root/ -> /boot/ ?
  5. Hey, so i use a automatic script in the go file to grab my keyfile and place it in /root/keyfile Is it correct that that is RAM which gets deleted when server is shutdown?
  6. Hey, why is my thread locked it spreads now it not only locks unraid, it also locks threads...
  7. I have same problem and i have no gigabyte board or extra network card. There must any change in latest RC, RC2 also hard locks for me. 6.6.6 is stable. Did u all change ur MTU? ichanged mine to 1436. Maybe its only hard locking when u chagned MTU.
  8. Okay, i can confirm that RC2 is also not working. I cant create error log sadly. Something must have changed from RC1 on, i never had that problem.
  9. Hey, i would like to have an option to only display active and favorited dockers on dashboard. So i can see disabled dockers (if they are a favorite, or what ever you wanna call it) on the dashboard. Usecase, e.g. i have a ts3 server which i only want to enable when i use it. Its far more easy to click on it on the dashboard then on the docker tab, if you have many dockers.
  10. fingeres crossed, i complete my migration to fully encrypted array and cache and installed RC2, until now (10% parity) it didnt became unreachable, lets see.
  11. Maybe hardlock has to do with MTU because i changed my to 1436, does anybody know if rc2 fixes that issue?
  12. yeah, srry i missed that and asked for move, but no one did
  13. Okay, i plugged a vga monitor in... and like last time, it showed normal login: password: fans are running full speed. No f ing error in syslog, NOTHING, it just stopped working. (i opend terminal and used screen to tail -f the syslog - so this should work) Im happy i was able to downgrade before it happend again. - but i really loved that new style. Last log 1 is 41C, adjusting fan speed from: 111 (43% @ 0rpm) to: 39 (15% @ 0rpm) Jan 24 01:58:39 Unraid-Server login[21545]: ROOT LOGIN on '/dev/pts/2' Jan 24 01:59:12 Unraid-Server emhttpd: req (17): cmd=/plugins/NerdPack/scripts/packagemanager&arg1=--download&csrf_token=**************** Jan 24 01:59:12 Unraid-Server emhttpd: cmd: /usr/local/emhttp/plugins/NerdPack/scripts/packagemanager --download Jan 24 01:59:12 Unraid-Server nerdpack: Processing Packages... Jan 24 01:59:12 Unraid-Server nerdpack: lynx-2.8.8rel.2 package up to date, checksum ok. Jan 24 01:59:13 Unraid-Server nerdpack: perl-5.26.1 package up to date, checksum ok. Jan 24 01:59:13 Unraid-Server nerdpack: Downloading python-2.7.15-x86_64-3.txz package... Jan 24 01:59:30 Unraid-Server nerdpack: python-2.7.15-x86_64-3.txz package download sucessful! Jan 24 01:59:30 Unraid-Server nerdpack: Installing python-2.7.15 package... Jan 24 01:59:36 Unraid-Server nerdpack: Downloading screen-4.6.2s-x86_64-2.txz package... Jan 24 01:59:39 Unraid-Server nerdpack: screen-4.6.2s-x86_64-2.txz package download sucessful! Jan 24 01:59:39 Unraid-Server nerdpack: Installing screen-4.6.2s package... Jan 24 01:59:39 Unraid-Server nerdpack: unionfs-fuse-0.26 package up to date, checksum ok. Jan 24 01:59:39 Unraid-Server nerdpack: Downloading utempter-1.1.6-x86_64-2.txz package... Jan 24 01:59:40 Unraid-Server nerdpack: utempter-1.1.6-x86_64-2.txz package download sucessful! Jan 24 01:59:40 Unraid-Server nerdpack: Installing utempter-1.1.6 package... Jan 24 01:59:41 Unraid-Server nerdpack: vim-7.4.1938 package up to date, checksum ok. Jan 24 01:59:41 Unraid-Server nerdpack: Cleaning up packages... Jan 24 01:59:41 Unraid-Server nerdpack: All packages processed... Last log 2 Jan 24 02:05:56 Unraid-Server autofan: Highest disk temp is 44C, adjusting fan speed from: 39 (15% @ 0rpm) to: 111 (43% @ 0rpm) Jan 24 02:16:02 Unraid-Server autofan: Highest disk temp is 41C, adjusting fan speed from: 111 (43% @ 0rpm) to: 39 (15% @ 0rpm) Jan 24 02:26:08 Unraid-Server autofan: Highest disk temp is 43C, adjusting fan speed from: 39 (15% @ 0rpm) to: 87 (34% @ 0rpm) Jan 24 02:35:33 Unraid-Server ool www[17978]: /usr/local/emhttp/plugins/unbalance/scripts/stop Jan 24 02:35:38 Unraid-Server ool www[6500]: /usr/local/emhttp/plugins/unbalance/scripts/start Jan 24 02:35:38 Unraid-Server sudo: root : TTY=unknown ; PWD=/usr/local/emhttp ; USER=nobody ; COMMAND=/usr/bin/bash -c /usr/local/emhttp/plugins/unbalance/unbalance -port 6237
  14. I already told you that its hard to do that. My wife restartet the server in the morning but still i couldnt access it. I try again now. I let a "screen" tail -f syslog to array run the whole night, so maybe ther is something. Edit: i cant do anything anymore, when i hard reset can i acces the server for like 1 min, that was it.
  15. It happend again. This night. It just loses network connection. - its active when i look on router (unraid ip, few bytes in and out), but not u cant connect to it, also all plugins, dockers and vms loses connectifty. Ill upload log as soon as i come home. It must be the new RC, because atleast 2 other ppl report it. But mysterios is that tehy have ryzen, and i dont. Can someone please move this thread into the correct forum?
  16. Dont know, only really thing i changed was SSL and XFS encryption and newest RC. I try to get the logs working
  17. upps.. please move it. What information exact? I cant give logs when nothing is logged... But like i said i try again. It might have something to do with unbalance and or file integry plugin!?
  18. Hey, so about 2-3 hours running, unraid is no longer reachable. Its now the second time. Not via HTTP or HTTPS or SSH. Its pingable, but not more. I plugged VGA in and it says normal "reachable via ip here login: " I try to shut it down non forcefully (last time i had to do it), so i can have some logs. I had loggin open while it happend this time.. but nothing special Jan 23 16:38:14 Unraid-Server autofan: Highest disk temp is 41C, adjusting fan speed from: 111 (43% @ 0rpm) to: 39 (15% @ 0rpm) was last line All docker non reachable. all plugins also. Edit: so i waited 20 min after pressing shutdown (on hardware) It says collecting informations... but nothing happens (normal it takes 1-2 min). I had to force it down again... ive attached my server diag after the last shutdown. unraid-server-diagnostics-20190123-1713.zip
  19. Next (connectifity) shutdown, maybe uptime of 1-2hours, found nothing in logs.... try again with #!/bin/bash mkdir -p /boot/logs FILENAME="/boot/logs/syslog-shutdown-$(date +%Y-%m-%d).txt" tail -f /var/log/syslog > $FILENAME
  20. I let now run: #!/bin/bash mkdir -p /boot/logs FILENAME="/boot/logs/syslog-shutdown-$(date +%s).txt" tail -f /var/log/syslog > $FILENAME
  21. already did, but couldnt get any usefull logs, tried 3 times. Im back on 6.6 stable now uptime 24hours +
  22. @limetech do you know if the rc2 helps maybe agains the "losing connection" bug?
  23. dont understand why syslog works for u, for me if it locks, there is just nothing in log at all.. reverted to latest stable, not useable.
  24. hmm... would mover automatic move it back to cache then?