Bobat
-
Posts
50 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Posts posted by Bobat
-
-
54 minutes ago, JorgeB said:
Do you have a monitor plugged in? If not using a VGA or HDMI dummy plug *might* help.
I did have a monitor plugged in via an HDMI KVM. I plugged the monitor directly into the server and it seems to have stopped. Thanks!
EDIT:
I spoke too soon, it stopped for about 15 minutes and then started doing it again. -
I'm getting the "EDID block 0 is all zeroes" error filling up my log on 6.11.0 final. I saw this on 6.11rc4 as well (never tried rc5). Rolling back to rc3 makes it go away. I saw this thread suggesting that blacklisting the GPU driver may fix it, but I use the integrated GPU for Plex transcoding so I don't think that's a viable solution for me. Any other ideas?
-
It goes in your nginx.conf. In mine, it's right after the events{} block and before the http{} block.
-
On 11/15/2020 at 8:14 AM, learningunraid said:
How many Port Forwarding PIA allows?
The US servers don't look like they support port forwarding. For the servers that do, it looks like you're limited to a single port. I don't use the function personally, so I'm not 100% sure on that.
-
On 10/23/2020 at 7:27 PM, learningunraid said:
Hello, Mine is not resolved yet. I am having the same issue. What to do?
If you're using PIA, make sure you're using the most up to date ovpn config files from the PIA site. They just recently retired a bunch of legacy servers. My config file was pointing to one of those old servers and I couldn't figure out why it wouldn't connect anymore. Download the default Nextgen config files and make sure you're using the current server names.
- 1
-
This is definitely possible. I do something very similar with my custom domain and Cloudflare. You need to set up stream proxying in your nginx.conf file.
stream { # Defining upstream servers for proxied traffic upstream tcp_backend { server 123.456.7.8:9443; } upstream udp_backend { server 123.456.7.8:1194; } # Defining protocols and ports for data to be proxied. server { proxy_connect_timeout 300s; proxy_timeout 300s; listen 9443; proxy_pass tcp_backend; } server { proxy_connect_timeout 300s; proxy_timeout 300s; listen 1193 udp; proxy_pass udp_backend; } }
Where 123.456.7.8 is the internal IP address of your OpenVPN server.
-
Lol. Less than an hour after posting that I got one Downgraded again.
-
24+ hours since upgrading to 6.5.1-rc1 and no call traces. Looks good.
-
3 hours ago, Jobine said:
Since the last update, my unraid server gives me some Call Trace errors.
Ideas ?
From your syslog:
QuoteMar 17 09:24:21 Serveur kernel: BUG: unable to handle kernel NULL pointer dereference at 0000000000000038
Mar 17 09:24:21 Serveur kernel: IP: tcp_push+0x4e/0xee
Mar 17 09:24:21 Serveur kernel: PGD 80000002431a8067 P4D 80000002431a8067 PUD 24319b067 PMD 0
Mar 17 09:24:21 Serveur kernel: Oops: 0002 [#1] PREEMPT SMP PTISeveral people (including myself) are having the same issue. See here, here, and here. I've downgraded back to 6.4.1 and everything's good for me now. I'll try again after the next release to see if a new kernel patch solves it.
-
I've also rolled back to 6.4.1 and have been OK so far.
-
On 3/13/2018 at 9:02 PM, interwebtech said:
Plex has crashed hard (gone from network) twice today with Call Traces (that plex is "tainted") in the logs. Logs attached.
ps. I have since updated to 6.5.0 with all fingers crossed.tower-diagnostics-20180313-1741.zip
ps.s While in farked state, I saw in Docker manager it showed as "unhealthy" under Log heading column. dunno what that means.
Have you had any call traces or kernel oops since moving to 6.5.0? I’m having a similar issue with Plex since 6.5. Considering a rollback to 6.4 to see if it goes away. Are you using linuxserver’s docker by chance?
-
I’ve had a few kernel oops and call traces lately. Any ideas?
-
Got 2 of these from Amazon on Black Friday. 8TB Seagate Barracuda Compute inside (ST8000DM004). Great deal!
-
Thanks. I think I initially misunderstood how dual parity was working and thought that both parity drives had to be available to have protection in a dual-parity setup. After reading this I get why having either of the parity drives available gives me one-drive failure tolerance while the other parity is rebuilding.
So is Parity 1 always the XOR and Parity 2 is the Reed-Solomon? So I want to replace Parity 1 with the new larger drive, let it rebuild, and then unassign Parity 2?
-
Here is my current config:
2 parity drives (3tb each)
1 cache drive (1tb ssd)
12 data drives (mix of sizes from 1 - 3tb)
I just bought 2 8tb drives on a black friday deal. The goal is to both increase the capacity of the array and consolidate and eliminate one of the smaller drives. I think the dual parity was overkill, so the final config will be a single 8tb parity drive and the other 8tb drive will be put into the array as a data drive. I think the steps for this would be:
- Stop the array
- Unassign both of the parity disks
- Assign one of the 8tb drives as parity, leave the old parity disks unassigned
- Start the array
- Wait for parity to rebuild
- Power down, pull one of the old 1tb data disks and replace with the other 8tb disk (precleared previously)
- Assign the new 8tb drive into the old slot, let it rebuild from parity
- Preclear the old parity disks, add them to the array as data disks
Sound right or am I missing something?
-
http://lime-technology.com/forum/index.php?topic=12767.msg259006#msg259006
Step-by step in is in the zip file referenced in the post. I just did this myself for the first time a few days ago. I had the "failed to initialize PAL" error at step 5, but luckily I had another PC on hand I could use to finish the procedure.
-
Hi,
Is anyone having problems connecting to the Crashplan Central service since the update? I've followed the posts in the last couple of pages to restore connection from my Windows box to the Crashplan docker, but the backup engine can't connect to the online service.
Any ideas?
SR
I was having the same issue post upgrade. Here's what I did to restore connectivity to Crashplan Central:
[*]Stop the Crashplan docker
[*]Backup your my.service.xml file in your Crashplan docker config folder - mine was in /mnt/cache/appdata/crashplan/conf/
[*]Edit my.service.xml and remove the hash string between the <autoLoginPasswordHash> tags
[*]Change the text between the <autoLogin> tag from "true" to "false"
[*]Start the Crashplan docker
[*]Launch the GUI client (either through Windows or the MATE, whichever you use) and sign in to your Crashplan account when prompted then close the client
[*]Stop the Crahsplan docker
[*]Edit my.service.xml and change the text between the <autoLogin> tag back to "true"
[*]Start the Crashplan docker again
Confirm through the GUI client that everything connected and your backups are working again. I don't know if toggling the autoLogin part is strictly necessary, you may only need to remove your old password hash, but this worked for me.
-
The binhex delugevpn container is back. Going to play around with it tonight.
-
Working now, thanks for the quick fix!
-
Just did an update on Owncloud from gfjardim's repository. Now Owncloud won't start and I'm seeing this repeated in my logs:
[17-Dec-2014 16:08:46] ERROR: failed to load configuration file '/etc/php5/fpm/php-fpm.conf' [17-Dec-2014 16:08:46] ERROR: FPM initialization failed [17-Dec-2014 16:08:47] ERROR: failed to open configuration file '/etc/php5/fpm/php-fpm.conf': No such file or directory (2) [17-Dec-2014 16:08:47] ERROR: failed to load configuration file '/etc/php5/fpm/php-fpm.conf' [17-Dec-2014 16:08:47] ERROR: FPM initialization failed [17-Dec-2014 16:08:48] ERROR: failed to open configuration file '/etc/php5/fpm/php-fpm.conf': No such file or directory (2) [17-Dec-2014 16:08:48] ERROR: failed to load configuration file '/etc/php5/fpm/php-fpm.conf' [17-Dec-2014 16:08:48] ERROR: FPM initialization failed [17-Dec-2014 16:08:49] ERROR: failed to open configuration file '/etc/php5/fpm/php-fpm.conf': No such file or directory (2) [17-Dec-2014 16:08:49] ERROR: failed to load configuration file '/etc/php5/fpm/php-fpm.conf' [17-Dec-2014 16:08:49] ERROR: FPM initialization failed
Anyone else having an issue?
-
The OpenVPN server plugin are now functional on beta 12!! Thanks to dmacias for your kind support!
//Peter
I can confirm that the server is up and running on my beta12 box. Thanks for the quick turnaround!
-
Does this plugin need to be updated for beta12? I just tried installing the 64 bit server and the config page comes up blank. Not sure if it's my issue or the plugins. I installed from the web GUI and didn't see any errors.
-
Had time to try this out over the weekend. Working great, thanks!
-
Any way to expose the nginix.conf file itself? I think that editing that file is necessary to set up shared memory spaces which are needed for things like rate limiting and connection limiting.
6.11.0 final - EDID block 0 is all zeroes error
in General Support
Posted
Sort of. My OPNsense router was also plugged into the same monitor, so I think after 15 minutes of inactivity the monitor was automatically switching over to the other input and the messages would start up again. I unplugged the other cable and it seems to be stable now. I rarely need a monitor plugged into either machine, so maybe I'll try one of those HDMI dummy plugs rather than keeping the monitor on all of the time.