vw-kombi

Members
  • Posts

    220
  • Joined

  • Last visited

Everything posted by vw-kombi

  1. It’s been the same build since it’s first installation. Been rock solid. Been through a number of unraid versions. Only he changes have been disk upgrades and removal of the 4 port Nic a while back when I stopped using the pfsense VM.
  2. No worries. I see posts saying 'upload diagnostics' when they are not there, so i thought i had better. Hopefully I can go another 3 years without seeing this.
  3. At about 03;20 the system went down. I notice a kernel panic on the screen. I have never had that before. Only system change is about 2 weeks ago - moved an nvme drive from unassigned devices to cache-nvme. System always been stable. Had to power off/on and the usual parity check now for a few days. Diagnostics is attached if anyone would like to comment ? Thanks in advance. tower-diagnostics-20211008-0715.zip
  4. Am I missing something here ? Emby can connect to tvh natively to get the streams ? What is the point if this docker ? My emby has an m3u tuner as such - http://192.168.1.202:9981/playlist/channels.m3u That is the IP address of my tvh.
  5. Firstly, the Emby Beta was updated around the same day as the Unraid server, so this may be emby's issue, but may also be something I have to configure on unraid for the 6.9.1 upgrade (I was on 6.8.3 beforehand). The issue - the emby conversion process is burning in closed captions - it did not used to do that. I have a cheap NVidia GPU card in my server as it is AMD with no onboard graphics and needed something to boot with. I dont pass it in to VM's or anything. I notice some stuff in the 6.9.x about making mods for built in graphics drivers - not sure if this relates to the issue. The emby server reports this in the hardware detection log at startup - I dont remember this being there before, as I have 8 CPU's and was software encoding. Emby is set to NO for 'Enable hardware transcoding' : "Devices": [ { "DeviceIndex": 0, "DeviceInfo": { "VendorName": "NVIDIA Corporation", "DeviceName": "GK208B [GeForce GT 710]", "SubsytemVendorName": "ZOTAC International (MCO) Ltd.", "VendorId": 4318, "DeviceId": 4747, "SubsytemVendorId": 6618, "SubsytemDeviceId": 21344, "DevPath": "/sys/bus/pci/devices/0000:05:00.0", "IsEnabled": 0, "IsBootVga": 1, "Error": { "Number": -1, "Message": "Failed to open the drm device (null)"
  6. I noticed the backups are smaller than my orginals. I have no idea why mine gained the extra files over time, likely not needed now. some are file system check files I believe. I may do the restore procedure and format of the USB to 'freshen it all up'
  7. I got it all working, had a play, then just removed the port forward so the remote stuff 'con's' are not there. More stuff may be added over time so I am happy to leave it as a glorified USB saving device until then. My remote access requirements are covered by tailscale to all my devices securely using wireguard (2FA linked to gmail) with no need of opening ports, firewall mods, ssl certs etc etc.
  8. With regards to port forwarding, am I able to enter the actual subnets that require forwarding, rather than anyone on the internet ? I currently only allow cloudflare IP's to access my home nginx server and re-direct that way. I have in the past used tailscale for access to unraid, and various other servers securely with zero config.
  9. another week and no crashes - lets assume that is the back of it!!!!
  10. This started happening to me as of today. My DNS however is set to cloudflares 'newer' 1.1.1.2 and 1.0.0.2 DNS servers. The ones with malware protection are 1.1.1.2. Maybe whatever unraid is using has got onto that list of nasties ?
  11. Been 4 days and no console crash. Fingers crossed it has settled down.
  12. Thanks for that - the first issue was waiting for me to climb in the loft of all places. I replaced my pfsense with ubiquiti USG (all on another thread as pfsense VM let me down), so I had to change the wifi's. This old laptop up in the loft is taking CCTV and storing it there every 5 minutes....... so robbers can be recorded and if they steal the unraid server, they are still on film. That is fixed now. Its just the console that is crashing. That support thing has not been an issue for me in the years of running unraid.
  13. Nope....... I assumed the diagnostics was wanted when the issue was in place. The issue causes no console, so I could not use the console to stop the array - or read the flash drive. In hindsight, I assume I could have figured out how to copy the diagnostics from the flash via the command line - as in I could cd to there, but not sure how I would have copied it off there.
  14. Oh dear - after restarting this c.php-fpm this time, all my console is white (not black) and in the top right I have 'missing key file' in red. If I click on that, and try to paste in my install key from the email from years back, I get Error (1) the bottom of the screen keeps f;ashing something about 'starting services', then warning something but it is too quick. to make matters worse, I cant stop the array as it says 'mover is running' to do a restart. In the end - a power off and on with the big button - and now the parity check I could do without !!!!!!
  15. And this has happened again. While it was stopped, I took the liberty to again run the disagnistics from the command line. Pulled the flash drive and inserted it into the PC and copied the zip file to here as instructed. tower-diagnostics-20210329-1829.zip
  16. so this has happened again. This time, I just restarted php-fpm. root@Tower:~# /etc/rc.d/rc.php-fpm restart Gracefully shutting down php-fpm . done Starting php-fpm done root@Tower:~# This MUST be an issue with the latest unraid release - as I have never had this before. Do I raise this as an issue ? I just dont seem to get any replies. I seem to just be posting replies to my self.
  17. Ubiquiti USG is in and operational. Prob about 4 hours to move about 2 years of pfsense config/tweaking onto it. I must say I am loving the interface. VPN's requirements now being done with windows VM's. Was initially worried about the IDS/IPS limiting routing to 85Mbps, but I can still saturate my 100Mbps internet plan.
  18. more searching and then I found this which is the missing piece - whatever that is/does : /etc/rc.d/rc.php-fpm restart
  19. So.... broke out the kill command....... root@Tower:~# /etc/rc.d/rc.nginx stop Shutdown Nginx gracefully... root@Tower:~# ps -ef | grep nginx nobody 2725 9941 0 02:00 ? 00:02:16 nginx: worker process nobody 2726 9941 0 02:00 ? 00:00:25 nginx: worker process root 9243 1 0 Mar23 ? 00:00:00 nginx: master process /usr/sbin/nginx -c /etc/nginx/nginx.conf root 9244 9243 0 Mar23 ? 00:05:34 nginx: worker process is shutting down root 9935 9543 0 Mar23 ? 00:00:00 s6-supervise nginx root 9941 9935 0 Mar23 ? 00:00:00 nginx: master process /usr/sbin/nginx -c /config/nginx/nginx.conf nobody 9962 9941 0 Mar23 ? 00:18:53 nginx: worker process is shutting down nobody 14112 13786 0 04:40 ? 00:00:00 nginx: master process nginx -c /opt/nginx.conf nobody 14114 14112 0 04:40 ? 00:00:00 nginx: worker process root 32312 15859 0 16:02 pts/2 00:00:00 grep nginx root@Tower:~# kill 9244 root@Tower:~# ps -ef | grep nginx nobody 2725 9941 0 02:00 ? 00:02:16 nginx: worker process nobody 2726 9941 0 02:00 ? 00:00:25 nginx: worker process root 3809 15859 0 16:03 pts/2 00:00:00 grep nginx root 9935 9543 0 Mar23 ? 00:00:00 s6-supervise nginx root 9941 9935 0 Mar23 ? 00:00:00 nginx: master process /usr/sbin/nginx -c /config/nginx/nginx.conf nobody 9962 9941 0 Mar23 ? 00:18:53 nginx: worker process is shutting down nobody 14112 13786 0 04:40 ? 00:00:00 nginx: master process nginx -c /opt/nginx.conf nobody 14114 14112 0 04:40 ? 00:00:00 nginx: worker process root@Tower:~# kill 9262 -bash: kill: (9262) - No such process root@Tower:~# ps -ef | grep nginx nobody 2725 9941 0 02:00 ? 00:02:16 nginx: worker process nobody 2726 9941 0 02:00 ? 00:00:25 nginx: worker process root 5650 15859 0 16:03 pts/2 00:00:00 grep nginx root 9935 9543 0 Mar23 ? 00:00:00 s6-supervise nginx root 9941 9935 0 Mar23 ? 00:00:00 nginx: master process /usr/sbin/nginx -c /config/nginx/nginx.conf nobody 9962 9941 0 Mar23 ? 00:18:53 nginx: worker process is shutting down nobody 14112 13786 0 04:40 ? 00:00:00 nginx: master process nginx -c /opt/nginx.conf nobody 14114 14112 0 04:40 ? 00:00:00 nginx: worker process root@Tower:~# /etc/rc.d/rc.nginx stop Nginx is not running root@Tower:~# /etc/rc.d/rc.nginx status Nginx is not running root@Tower:~# /etc/rc.d/rc.nginx start Starting Nginx server daemon... root@Tower:~# And so something different - both the remote desktop and the unraid gui console are just spinning when they try to go to http://192.168.1.7/main (my console IP), then after about 30 seconds, 500 Internal Server Error nginx. I need some help / ideas. and if this cant be fixed for the command line (it should be), then console commands for stop array and restart.
  20. Seems it cant stop it : root@Tower:~# /etc/rc.d/rc.nginx stop Shutdown Nginx gracefully... root@Tower:~# /etc/rc.d/rc.nginx status Nginx is running root@Tower:~# /etc/rc.d/rc.nginx start Nginx is already running root@Tower:~# /etc/rc.d/rc.nginx status Nginx is running root@Tower:~#
  21. So, I ran /etc/rc.d/rc.nginx restart, and it said : Checking configuration for correct syntax and then trying to open files referenced in configuration... nginx: the configuration file /etc/nginx/nginx.conf syntax is ok nginx: configuration file /etc/nginx/nginx.conf test is successful Shutdown Nginx gracefully... Nginx is already running And still I cant access the console. Can anyone give me some sort of direction ? I got no assistance from my last post so I am looking for some love.
  22. as ssh, dockers, networking and nas shares are all fine, this is only holding me up...... I have run a diagnostocs from the commnd line. Now I have to figure out how to restart nginx it seems from the googling.
  23. Lost console access. Dockers and shares still working. I had a preclear running on a 10TB new drive, and I had a vnc connection to a VM. I assume I can run something from the command line to restart this ? I dont really want to power down and up. Only other change is I upgraded to 6.9.1 three days back. No issues till now. My VNC session to the VM is also still working.
  24. No-one offered any help so I have decided to dump pfsense. So I will be deleting the VM's for pfsense, removing the 4 port nic and free'ing up a laptop that was the backup pfsense device. I can buy 2 x Ubiquiti USG Security gateways for the price of one netgate pfsense appliance. I already use Ubiquity wifi so this will give me a nice load of features in the unifi controller. I have researched the USG devices and figured out what I can and cant do on it - specifically native multi location openvpn VPN's it seems. I know you can do stuff at the command level on USG to get that working, and I may get around to that one day. I will either move all my dockers back to the bridge network and then I can use the VPN dockers to route, or I will add a few VM's that have full time VPN turned on and run the stuff I need through them. So I will be deleting the VM's for pfsense, removing the 4 port nic and free'ing up a laptop that was the backup pfsense device.
  25. Should I worry about this in the log file ? [info] Run tor as service on port 9119 Starting tor daemon...Mar 24 02:01:06.000 [warn] You specified a public address '0.0.0.0:9119' for SocksPort. Other people on the Internet might find your computer and use it as an open proxy. Please don't allow this unless you have a good reason. done.