PBS won't fully start? [RESOLVED, user error]

[orgguy]

PBS installed into a VM running on Synology. Installed fine, rebooted, got stuck before the login screen.
Last thing I see on console is:



Hitting enter doesn't get me anything. I can ssh into the machine, and all looks OK. Nothing obvious in /var/log/..., and for example I see these processes running:

root 535 0.1 0.4 316668 17616 ? Ssl 12:40 0:01 /usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-api backup 619 0.5 0.5 452844 23372 ? Ssl 12:40 0:04 /usr/lib/x86_64-linux-gnu/proxmox-backup/proxmox-backup-proxy

so seems like things have sort of started up. However, I don't get anything resembling a webserver response from port 8007 (even though it's being listened to by the -backup-proxy process according to lsof.

It's possible there's a networking issue (I gave the machine a bogus hostname), but it can resolve outbound just fine. For example, via ssh I was able to apt update and upgrade successfully.

Thoughts? I was expecting a root login prompt with the pointer to the :8007 URL...

 

[dcsapak]

can you post the output of 'ss -tlpn' and the journal/syslog since the boot?

what happens if you do

curl -k -vv https://localhost:8007/

on the pbs ?

 

[orgguy]

I'm an idiot, I was not attempting to hit it with https. And I guess because this was my first post to the forum it didn't instantly post, so I couldn't update it until afterwards. Thanks for your help Dominik, you were definitely on the right track!

Still kind of confused why it never printed out the banner line that states the URI, had I see that I probably would have realized it should be https. But definitely my bad

 

[casalicomputers]

Hello I'm posting a bit late, but I was having the same issue, the machine worked fine,
but the system dropped the noVNC console connection during the init process, right when mounting /.
So the DSM Virt Manager noVNC console kept getting stuck at the stage posted in the screenshot above.
At least that's what I think was happening.

PBS worked fine, but if the OS lost network connectivity for some reason there would be be no way to interact with the system...
Backup Server 3.1-2 was installed with the Proxmox provided ISO file.
qemu guest agent was also installed.

DS923+
DSM 7.2.1-69057 Update 3
AMD Ryzen R1600 2.6 GHz

After having ssh int' the machine i noticed the following warning from dmesg:

[ 5.252751] vmwgfx 0000:00:02.0: vgaarb: deactivate vga console [ 5.274364] Console: switching to colour dummy device 80x25 [ 5.274948] vmwgfx 0000:00:02.0: [drm] FIFO at 0x00000000fe000000 size is 64 kiB [ 5.274988] vmwgfx 0000:00:02.0: [drm] VRAM at 0x00000000fd000000 size is 16384 kiB [ 5.275021] vmwgfx 0000:00:02.0: [drm] Running on SVGA version 2. [ 5.275038] vmwgfx 0000:00:02.0: [drm] Capabilities: rect copy, cursor, cursor bypass, cursor bypass 2, [ 5.275043] vmwgfx 0000:00:02.0: [drm] *ERROR* vmwgfx seems to be running on an unsupported hypervisor. [ 5.275058] vmwgfx 0000:00:02.0: [drm] *ERROR* This configuration is likely broken. [ 5.275069] vmwgfx 0000:00:02.0: [drm] *ERROR* Please switch to a supported graphics device to avoid problems. [ 5.275082] vmwgfx 0000:00:02.0: [drm] DMA map mode: Caching DMA mappings. [ 5.275146] vmwgfx 0000:00:02.0: [drm] Legacy memory limits: VRAM = 16384 kB, FIFO = 64 kB, surface = 524288 kB [ 5.275151] vmwgfx 0000:00:02.0: [drm] MOB limits: max mob size = 0 kB, max mob pages = 0 [ 5.275155] vmwgfx 0000:00:02.0: [drm] Maximum display memory size is 16384 kiB [ 5.275159] [drm:vmw_probe [vmwgfx]] *ERROR* Hardware has no pitchlock [ 5.275284] vmwgfx: probe of 0000:00:02.0 failed with error -38

So I just shut down the machine and switched the video card on the Virt Manager from vmvga to vga, problem solved.
Hope this helps.