pixelserv Diversion - pixelserv not running

  • ATTENTION! You'll notice a Prefix dropdown when you create a thread. If your post applies to one of the topics listed, please use that Prefix for your post. When browsing the thread list you can use the Prefix to filter the view.
  • ATTENTION! As of November 1, 2020, you are not able to reply to threads 6 months after the thread is opened if there are more than 500 posts in the thread.
    Threads will not be locked, so posts may still be edited by their authors.
    Just start a new thread on the topic to post if you get an error message when trying to reply to a thread.

root

Occasional Visitor
Hi,

I have a problem, Diversion says that Pixelserv is not running. I've tried to restart it through Diversion and I've tried to reinstall Diversion with no success, Pixelserv is still not running.

I can ping Pixelserv IP-address 192.168.1.2 but when I try to browse to 192.168.1.2 or 192.168.1.2/ca.crt it says "connection failed".

What else can I try to pinpoint the problem?

Thanks in advance!
 

elorimer

Very Senior Member
Anything in the log?
Are you running an Openvpn server on port 443?
 

root

Occasional Visitor
Jan 15 08:34:24 Diversion: created br0:pixelserv-tls for 192.168.1.2
Jan 15 08:34:24 pixelserv-tls[16170]: pixelserv-tls 2.3.1 (compiled: Nov 29 2020 18:27:57 flags: tfo tls1_3) options: 192.168.1.2
Jan 15 08:34:24 Entware (aarch64-k3.10): Started pixelserv-tls (Diversion)
Jan 15 08:34:24 kernel: CPU: 1 PID: 16170 Comm: pixelserv-tls

No Openvpn server running.
 

Jack Yaz

Part of the Furniture
router model? firmware version?
 

elorimer

Very Senior Member
The AC86U defaults to a 192.168.50.1 address, so did you change your LAN to 192.168.1.1? If the pool is 50.xx your pixelserv address should be 50.2. Does the LAN pool start above 192.168.1.2, so there is no other device on that address?
 

root

Occasional Visitor
The AC86U defaults to a 192.168.50.1 address, so did you change your LAN to 192.168.1.1? If the pool is 50.xx your pixelserv address should be 50.2. Does the LAN pool start above 192.168.1.2, so there is no other device on that address?

I think I changed it when I first configured the router and LAN addresses starts at 1.3.
 

root

Occasional Visitor
I've stumbled upon something strange regarding my problem. I'm currently running the FTP-server on my AC86u, and the IP-address is 192.168.1.1 (my routers internal IP-address). But I can also use 192.168.1.2 to access the same FTP-server.. How and why is it running on both IP-addresses? Maybe that's why pixelserv's not working? I've tried to disable "FTP share" in the GUI and then restart pixelserv, but I still can't get it up and running. If I disable both "FTP share" and pixelserv I can't ping 192.168.1.2 anymore. Any suggestions?
 

PeterR

Regular Contributor
You could use the netstat command to see what's running on 192.168.1.2, e.g.

netstat -lp | grep 192.168.1.2

I think you should already have the netstat binary installed.
 

root

Occasional Visitor
You could use the netstat command to see what's running on 192.168.1.2, e.g.



I think you should already have the netstat binary installed.

:/tmp/home/root# netstat -lp | grep 192.168.1.2
netstat: showing only processes with your user ID
udp 0 0 192.168.1.255:netbios-ns 0.0.0.0:* 26424/nmbd
udp 0 0 192.168.1.255:netbios-dgm 0.0.0.0:* 26424/nmbd

Even with the FTP-server turned on with active connection I can't see anything related to 192.168.1.2.
 

PeterR

Regular Contributor
There's nothing running on 192.168.1.2, is that what you expect? This is my result for a comparison:

tcp 0 0 192.168.131.2:www 0.0.0.0:* LISTEN 3641/pixelserv-tls
tcp 0 0 192.168.131.2:https 0.0.0.0:* LISTEN 3641/pixelserv-tls
udp 0 0 192.168.131.255:netbios-ns 0.0.0.0:* 1275/nmbd
udp 0 0 192.168.131.255:netbios-dgm 0.0.0.0:* 1275/nmbd
 

root

Occasional Visitor
There's nothing running on 192.168.1.2, is that what you expect? This is my result for a comparison:

I thought at first that i would see the FTP running on 192.168.1.2, but I did the command with grep 192.168.1.1 and I didn't see anything FTP related there either so.

I should see pixelserv running on 192.168.1.2 like you, I don't know why it won't start and I don't know where to troubleshoot.

I don't understand why I can access the FTP server from both 192.168.1.1 and 192.168.1.2.
 

dave14305

Part of the Furniture
The ftp server may listen on 0.0.0.0 (all interfaces) which is why it responded on .2. Run netstat -nltup to see what’s listening where.
 

PeterR

Regular Contributor
I thought at first that i would see the FTP running on 192.168.1.2, but I did the command with grep 192.168.1.1 and I didn't see anything FTP related there either so.

I should see pixelserv running on 192.168.1.2 like you, I don't know why it won't start and I don't know where to troubleshoot.

I don't understand why I can access the FTP server from both 192.168.1.1 and 192.168.1.2.
Do you see anything in the log, this is from mine when pixelsrv-tls comes up

Jan 27 07:50:52 kernel: usb 1-2: reset high speed USB device using ehci_hcd and address 2
Jan 27 07:50:53 avahi-daemon[829]: Registering new address record for 192.168.131.2 on br0.IPv4.
Jan 27 07:50:53 Diversion: created br0:pixelserv-tls for 192.168.131.2
Jan 27 07:50:53 pixelserv-tls[3641]: pixelserv-tls 2.3.1 (compiled: Nov 30 2020 13:01:15 flags: tls1_3) options: 192.168.131.2
Jan 27 07:50:53 Entware (armv7sf-k2.6): Started pixelserv-tls (Diversion)
Jan 27 07:50:53 kernel: ip_set: protocol 6
Jan 27 07:50:53 admin: Started tailtopd from /jffs/scripts/post-mount.
Jan 27 07:50:54 rc_service: service 3742:notify_rc restart_dnsmasq
Jan 27 07:50:54 rc_service: waitting "restart_dnsmasq" via ...
Jan 27 07:50:55 kernel: warning: process `unbound' used the deprecated sysctl system call with 1.40.6.
Jan 27 07:50:55 admin: Diversion Mounting Diversion WebUI as user2.asp
Jan 27 07:50:56 pixelserv-tls[3641]: Listening on :192.168.131.2:443
Jan 27 07:50:56 pixelserv-tls[3641]: Listening on :192.168.131.2:80
Jan 27 07:50:57 Diversion: restarted Dnsmasq to apply settings
 

root

Occasional Visitor
The ftp server may listen on 0.0.0.0 (all interfaces) which is why it responded on .2. Run netstat -nltup to see what’s listening where.
You're right, found this:

tcp 0 0 0.0.0.0:21 0.0.0.0:* LISTEN 12412/vsftpd

So now I know there's nothing else running on 192.168.1.2 that could interfere with pixelserv.

Do you see anything in the log, this is from mine when pixelsrv-tls comes up

Jan 28 14:10:25 Diversion: created br0:pixelserv-tls for 192.168.1.2
Jan 28 14:10:25 pixelserv-tls[19126]: pixelserv-tls 2.3.1 (compiled: Nov 29 2020 18:27:57 flags: tfo tls1_3) options: 192.168.1.2
Jan 28 14:10:25 kernel: pgd = ffffffc002535000
Jan 28 14:10:25 kernel: [00000010] *pgd=00000000128b0003, *pud=00000000128b0003, *pmd=0000000000000000
Jan 28 14:10:25 kernel: CPU: 1 PID: 19126 Comm: pixelserv-tls Tainted: P O 4.1.27 #2
Jan 28 14:10:25 Entware (aarch64-k3.10): Started pixelserv-tls (Diversion)
Jan 28 14:10:25 kernel: Hardware name: Broadcom-v8A (DT)
Jan 28 14:10:25 kernel: task: ffffffc0139ea1c0 ti: ffffffc005ed8000 task.ti: ffffffc005ed8000
Jan 28 14:10:25 kernel: PC is at 0x40733c
Jan 28 14:10:25 kernel: LR is at 0x407334
Jan 28 14:10:25 kernel: pc : [<000000000040733c>] lr : [<0000000000407334>] pstate: 60000000
Jan 28 14:10:25 kernel: sp : 0000007fe3971ba0
Jan 28 14:10:25 kernel: x29: 0000007fe3971ba0 x28: 0000000000000000
Jan 28 14:10:25 kernel: x27: 0000000000000000 x26: 0000000000000000
Jan 28 14:10:25 kernel: x25: 0000000000000000 x24: 0000000000000000
Jan 28 14:10:25 kernel: x23: 0000000000000000 x22: 0000000000000000
Jan 28 14:10:25 kernel: x21: 0000000000403eb0 x20: 0000000000000000
Jan 28 14:10:25 kernel: x19: 000000000040c4b0 x18: 0000000000000001
Jan 28 14:10:25 kernel: x17: 0000000000000000 x16: 0000000000000005
Jan 28 14:10:25 kernel: x15: 0000000000000028 x14: 0000000000000002
Jan 28 14:10:25 kernel: x13: 00000000000000a0 x12: 0101010101010101
Jan 28 14:10:25 kernel: x11: 0000000000000008 x10: 0101010101010101
Jan 28 14:10:25 kernel: x9 : 0000000000000000 x8 : 0000000000000038
Jan 28 14:10:25 kernel: x7 : 0000000000080000 x6 : 0000000000000000
Jan 28 14:10:25 kernel: x5 : 0000000000000000 x4 : 00000000093ed5f4
Jan 28 14:10:25 kernel: x3 : 0000000000000000 x2 : 0000000000000000
Jan 28 14:10:25 kernel: x1 : 0000000000000001 x0 : 0000000000000000

This comes up when I choose to restart pixelserv through diversion.
 

PeterR

Regular Contributor
You can check if the pixelserv-tls daemon is running using the rc script, i.e.


Code:
/opt/etc/init.d/S80pixelserv-tls check

if you set the switch for debug logging in diversion - diversion|ep|2| and add -l 5 then restart pixelserv-tls - see if you get more information in the log.
 

root

Occasional Visitor
You can check if the pixelserv-tls daemon is running using the rc script, i.e.


Code:
/opt/etc/init.d/S80pixelserv-tls check

if you set the switch for debug logging in diversion - diversion|ep|2| and add -l 5 then restart pixelserv-tls - see if you get more information in the log.

/tmp/home/root# /opt/etc/init.d/S80pixelserv-tls check
Checking pixelserv-tls (Diversion)... dead

Restared pixelserv with debug logging, didn't get anymore information:

Jan 29 08:30:15 Diversion: created br0:pixelserv-tls for 192.168.1.2
Jan 29 08:30:15 pixelserv-tls[8924]: pixelserv-tls 2.3.1 (compiled: Nov 29 2020 18:27:57 flags: tfo tls1_3) options: 192.168.1.2 -l 5
Jan 29 08:30:15 kernel: pgd = ffffffc00256d000
Jan 29 08:30:15 kernel: [00000010] *pgd=00000000129d2003, *pud=00000000129d2003, *pmd=0000000000000000
Jan 29 08:30:15 kernel: CPU: 0 PID: 8924 Comm: pixelserv-tls Tainted: P O 4.1.27 #2
Jan 29 08:30:15 Entware (aarch64-k3.10): Started pixelserv-tls (Diversion)
Jan 29 08:30:15 kernel: Hardware name: Broadcom-v8A (DT)
Jan 29 08:30:15 kernel: task: ffffffc012811540 ti: ffffffc0153bc000 task.ti: ffffffc0153bc000
Jan 29 08:30:15 kernel: PC is at 0x40733c
Jan 29 08:30:15 kernel: LR is at 0x407334
Jan 29 08:30:15 kernel: pc : [<000000000040733c>] lr : [<0000000000407334>] pstate: 60000000
Jan 29 08:30:15 kernel: sp : 0000007fe78d82b0
Jan 29 08:30:15 kernel: x29: 0000007fe78d82b0 x28: 0000000000000000
Jan 29 08:30:15 kernel: x27: 0000000000000000 x26: 0000000000000000
Jan 29 08:30:15 kernel: x25: 0000000000000000 x24: 0000000000000000
Jan 29 08:30:15 kernel: x23: 0000000000000000 x22: 0000000000000000
Jan 29 08:30:15 kernel: x21: 0000000000403eb0 x20: 0000000000000000
Jan 29 08:30:15 kernel: x19: 000000000040c4b0 x18: 0000000000000001
Jan 29 08:30:15 kernel: x17: 0000000000000000 x16: 0000000000000005
Jan 29 08:30:15 kernel: x15: 0000000000000028 x14: 0000000000000002
Jan 29 08:30:15 kernel: x13: 00000000000000a0 x12: 0101010101010101
Jan 29 08:30:15 kernel: x11: 0000000000000008 x10: 0101010101010101
Jan 29 08:30:15 kernel: x9 : 0000000000000000 x8 : 0000000000000038
Jan 29 08:30:15 kernel: x7 : 0000000000080000 x6 : 0000000000000000
Jan 29 08:30:15 kernel: x5 : 0000000000000000 x4 : 00000000059c25f4
Jan 29 08:30:15 kernel: x3 : 0000000000000000 x2 : 0000000000000000
Jan 29 08:30:15 kernel: x1 : 0000000000000001 x0 : 0000000000000000
 

PeterR

Regular Contributor
For some reason pixelsrv-tls is crashing upon startup, I can only suggest:
  • Remove any old certificate in /mnt/USB/entware/var/cache/pixelserv/
  • Run a disk check on your USB drive
 

root

Occasional Visitor
Tried removing och generating new certificates and doing a disk check on my USB drive, no luck..
 

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top