[Solved] Pine64 Crashes
#1
I've been using my Pine64 to host my Plex and Transmission torrent server. Lately, I've noticed that the server only stays alive for ~1 day before becoming unresponsive (meaning I cannot SSH into it, but the power light remains on). I'm hoping someone here has an idea or suspicion for what's going on because I'm at a loss.


Hardware setup:
  • Pine64 - 1GB board

  • Externally powered USB 2.0 hub

  • 1TB USB 3.0 Drive

  • 2TB USB 3.0 Drive
  • Heatsink on cpu
Below are the services that I'm currently using:
  • Plex Media Server (Plex application data is on 1TB drive, media is on 2TB drive)

  • Transmission daemon (writes to 1TB drive)

  • PlexPy (monitoring)

  • DynDNS (for easy-to-remember CNAME for Transmission + Plex)

  • sshd
I'm currently running Debian and here is my /var/log/messages: http://pastebin.com/RdYkpzCt

Any help would be appreciated.
  Reply
#2
Hey. The issue is caused by the transmission daemon - when I figure it out, I'll let you know. Currently doing a few other things too, and this is low on my priority list, but I'll get to it. If you come up with the solution first, do let me know plz Smile
You can find me on IRC, Discord and Twitter


  Reply
#3
(01-27-2017, 09:15 AM)Luke Wrote: Hey. The issue is caused by the transmission daemon - when I figure it out, I'll let you know. Currently doing a few other things too, and this is low on my priority list, but I'll get to it. If you come up with the solution first, do let me know plz Smile

Thank you!! Ok, I'm going to start digging through the logs and see what's going on too. Thanks for pointing me in the right track.

And yes, this is very low priority Smile
  Reply
#4
There are a few oddities that I have a feeling are somehow related, although I really don't know the root cause. For instance, forwarding port 22 will cause the pine to crash eventually (possibly due to attacks? Im running a webserver off of a 512mb board); not an issue for me, as I've got a VPN set up at home, and hence can ssh into the pine that way. Do you have any ports forwarded to your pine ?
You can find me on IRC, Discord and Twitter


  Reply
#5
(01-27-2017, 10:31 AM)Luke Wrote: There are a few oddities that I have a feeling are somehow related, although I really don't know the root cause. For instance, forwarding port 22 will cause the pine to crash eventually (possibly due to attacks? Im running a webserver off of a 512mb board); not an issue for me, as I've got a VPN set up at home, and hence can ssh into the pine that way. Do you have any ports forwarded to your pine ?

Yes, the following:

8181 - PlexPy
22 - SSH
9000 - Transmission web
49152-65535 - Transmission
32400 - Plex

To be honest, I don't use PlexPy outside my LAN. I do sometimes SSH outside my LAN, but I can change the port (unless port forwarding is the issue). My auth.log shows a TON of failed requests.

Note: I do have jail2ban set up with 6 max retries for ssh and a 10 minute ban.
  Reply
#6
Ok I changed some transmission settings:

* Reduced number of peers per torrent (100) and global peers (200).
* Added EVENT_NOEPOLL=1
* Added net.core.rmem_max = 16777216
* Added net.core.wmem_max = 4194304

Sadly, this didn't solve the problem.
  Reply
#7
I suggest you start by closing off port 22 and seeing if the server stays up. Give it a few days. If it turns out you have the same problem as I've had with exposing port 22 then either 1) we dig deeper into this and try to figure out whats causing it, or 2) work around it. If its not it then its surely transmission. Think you have some troubleshooting ahead of you ...
You can find me on IRC, Discord and Twitter


  Reply
#8
(01-27-2017, 06:46 PM)Luke Wrote: I suggest you start by closing off port 22 and seeing if the server stays up. Give it a few days. If it turns out you have the same problem as I've had with exposing port 22 then either 1) we dig deeper into this and try to figure out whats causing it, or 2) work around it. If its not it then its surely transmission. Think you have some troubleshooting ahead of you ...

Yep sounds good. I'm going to change the default sshd port to something other than 22 and going to stop port forwarding ssh so it's only accessible via LAN. Then, let's see what uptime we can keep.
  Reply
#9
Might be a little early, but disabling public SSH access definitely helped. Uptime increased from 1 day to 3 days and counting.
  Reply
#10
(01-31-2017, 12:29 AM)dedseason Wrote: Might be a little early, but disabling public SSH access definitely helped. Uptime increased from 1 day to 3 days and counting.

There you go. Also, I saw that a recent update to transmission daemon has solved the issue on that end. 

I will set up a 512mb board, open up port 22, log everything, and wait for it to die. I will share the log here and have smart ppl like pferrick and Xalius take a look at it.
You can find me on IRC, Discord and Twitter


  Reply


Possibly Related Threads...
Thread Author Replies Views Last Post
  Manjaro arm on pine64+ roel 2 190 10-19-2019, 05:13 AM
Last Post: roel
  Volumio for PINE64 Released mikelangeloz 11 6,573 03-22-2019, 09:25 AM
Last Post: llungster
  I2S Audio patches for Pine64+ uploaded to GitHub ramstadt 1 270 01-19-2019, 11:31 AM
Last Post: ramstadt
  Pine64: Minimal SDL config Max11 3 523 01-04-2019, 03:47 PM
Last Post: Max11
  Fedora 27 on Pine64 gregjo 18 7,326 01-02-2019, 10:42 PM
Last Post: heatfanjohn
  Official build procedure of ayufan pine64 r.tanaka 0 592 08-21-2018, 10:54 PM
Last Post: r.tanaka
  DKMS on kernel 3.10.107-pine64 obrienmd 5 734 06-21-2018, 05:45 PM
Last Post: evilbunny
  Programming languages support under PINE64 baryluk 5 3,177 03-09-2018, 01:52 AM
Last Post: kaokaobang
  Gentoo for pine64 - longsleep kernel incoherent 0 856 12-09-2017, 08:14 AM
Last Post: incoherent
  Fedora Running On Pine64! cztian 26 5,399 10-26-2017, 05:51 PM
Last Post: gregjo

Forum Jump:


Users browsing this thread: 1 Guest(s)