lewinator56

Forum Replies Created

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • in reply to: Unable to start the server in a chroot environment #26444
    Avatarlewinator56
    Participant

    The only problem now isĀ  I login to a white screen, I’ve tried the fix changing /usr/NX/etc/node.cfg, and it hasn’t worked,
    The desktop manager appears to be lightdm

    in reply to: Unable to start the server in a chroot environment #26443
    Avatarlewinator56
    Participant

    yep, thanks! that worked!

    in reply to: Unable to start the server in a chroot environment #26442
    Avatarlewinator56
    Participant

    I’ll give it a go and report back,

    sorry for the late reply, the notification went into spam

    in reply to: Unable to start the server in a chroot environment #25859
    Avatarlewinator56
    Participant

    so, i checked nxerror.log and its effectively the same as nxserver.log:

     

    20292 20292 10:56:21 870.199 Socket: WARNING! Can’t create the IPv4 socket.

    20292 20292 10:56:21 878.682 Socket: WARNING! Error is 13 ‘Permission denied’.

    20292 20292 10:56:21 878.737 Socket: WARNING! Can’t create the IPv6 socket.

    20292 20292 10:56:21 878.745 Socket: WARNING! Error is 13 ‘Permission denied’.

    20292 20292 10:56:21 878.767 Socket: WARNING! Can’t create any local socket.

    20292 20292 10:56:21 932.012 OpenSocketToListen: WARNING! Socket creation failed with error 13, ‘Permission denied’.

    mesg: ttyname failed: Inappropriate ioctl for device

     

    so, the chroot has access to the network as standard vnc and ssh work fine, as do normal network connections, its running on android 9 on a snapdragon 845 (ARM64).

    the environmet was set up using linux deploy (i know you obviously wont provide any support for that, iv’e already contacted the dev and its just a standard chroot environment so should have no differences).

    its set up as a separate linux image on the drive, rather than as a directory.

     

    i may well need to mount certain partitions to access the network hardware, but im suprised if this is the case as, like i’ve said, vnc and ssh work fine.

Viewing 4 posts - 1 through 4 (of 4 total)