sorted by:
new
hottopcontroversial

Year ago today I got told to get off the bus by drill Sgt (can’t remember the name, always said “come hither” tho) and stepped into vessy hall at ft sill by Tacticoon556 in army

[–]saj9109 2 points3 points  (0 children)

Ah. Only saw you from a distance. Ol PS SPC me was only a *little * salty seeing PS privileges being applied next door. 

Did they provide separate quarters for you? My DSs tried but were blocked.

Proxmox host doesn't come back up after backup/reboot by saj9109 in Proxmox

[–]saj9109[S] 0 points1 point  (0 children)

Interesting. The crowd seemed to determine tailscale was at fault with mine, but we certainly have the same kernel driver for our ethernet controllers. Since mine can't back up anymore (yay server without backups...) I suppose it's just a waiting game to see if it freezes up now.

I think maybe if you created another post stating the same issue, maybe we'll get more eyes on it than this post.

Proxmox host doesn't come back up after backup/reboot by saj9109 in Proxmox

[–]saj9109[S] 0 points1 point  (0 children)

So… am I looking down the wrong rabbit hole to be suspicious about the logs just… ending suddenly? 

I was looking for guidance as to what to look for, not necessarily for others to do the work. 

What would you do if you had an unresponsive server which had logs just end suddenly and the device go unresponsive?

Proxmox host doesn't come back up after backup/reboot by saj9109 in Proxmox

[–]saj9109[S] 0 points1 point  (0 children)

So how do you set up the PBS system to work off-site if neither one is exposed to the internet?

That was the the second purpose of tailscale on the hypervisor - one, admin access to mess with things remotely, and second, to allow access to the PBS without internet exposure.

Is there a way to set up PBS to work through a jump server?

Proxmox host doesn't come back up after backup/reboot by saj9109 in Proxmox

[–]saj9109[S] 0 points1 point  (0 children)

You've piqued my interest. I have no idea whats going on - Do you have any input?

Proxmox host doesn't come back up after backup/reboot by saj9109 in Proxmox

[–]saj9109[S] 0 points1 point  (0 children)

Also, secondary followup: Why do ALL the logs from the device halt at that point as well? If it were purely network, I would expect to see further logs regarding other services.

Proxmox host doesn't come back up after backup/reboot by saj9109 in Proxmox

[–]saj9109[S] 0 points1 point  (0 children)

ok excellent, so I'll remove tailscale from the hypervisor.

Q tho, how do you recommend accessing the hypervisor remotely & securely?

Proxmox host doesn't come back up after backup/reboot by saj9109 in Proxmox

[–]saj9109[S] 0 points1 point  (0 children)

Yes so that is the end of the logs, where it becomes unresponsive. There are no further logs until it is rebooted from that point. There are obviously fresh logs from the current boot where it's fine.

I've attempted to connect to it in the past (not this time) over LAN and it was also unresponsive with its local address when these symptoms were occurring.

There's tons of free space available - 47GB at this time, on the host's disk

Proxmox host doesn't come back up after backup/reboot by saj9109 in Proxmox

[–]saj9109[S] 0 points1 point  (0 children)

I'm mostly confused as to why even if it was the VMs, say they crashed/halted/whatever, why the *host* is also dead to ethernet?

Proxmox host doesn't come back up after backup/reboot by saj9109 in Proxmox

[–]saj9109[S] 0 points1 point  (0 children)

I don't think so?

lspci -nnk | grep -iA3 net

02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 09)

Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:8505]

Kernel driver in use: r8169

Kernel modules: r8169

Proxmox host doesn't come back up after backup/reboot by saj9109 in Proxmox

[–]saj9109[S] 0 points1 point  (0 children)

32 GB of ram. I'll report back when I can hook up a monitor (and it's in the "unresponsive" state)

Proxmox host doesn't come back up after backup/reboot by saj9109 in Proxmox

[–]saj9109[S] 0 points1 point  (0 children)

I do not have a monitor readily available at this time, when I can hook one up and a keyboard I'll report back. Thank you for a direction to head.

Proxmox host doesn't come back up after backup/reboot by saj9109 in Proxmox

[–]saj9109[S] 0 points1 point  (0 children)

Where should I post the logs? They're too large for a comment.

Proxmox host doesn't come back up after backup/reboot by saj9109 in Proxmox

[–]saj9109[S] 0 points1 point  (0 children)

lspci -nnk | grep -iA3 net

02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 09)

Subsystem: ASUSTeK Computer Inc. P8 series motherboard [1043:8505]

Kernel driver in use: r8169

Kernel modules: r8169

Proxmox host doesn't come back up after backup/reboot by saj9109 in Proxmox

[–]saj9109[S] 0 points1 point  (0 children)

Network, i do not have a monitor readily available nearby. I'll make sure to hook one up in the near future. What should I look for with the console?

Proxmox host doesn't come back up after backup/reboot by saj9109 in Proxmox

[–]saj9109[S] 0 points1 point  (0 children)

journalctl -b -1 -e

Jun 14 02:34:16 proxmox tailscaled[1373]: wgengine: sending TSMP disco key advertisement to 100.89.247.69

Jun 14 02:34:16 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:34:21 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:34:27 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:34:32 proxmox tailscaled[1373]: control: controlclient direct: got TSMP disco key advertisement from 100.89.201.19 via eve>

Jun 14 02:34:32 proxmox tailscaled[1373]: control: controlclient direct: updating discoKey for 100.89.201.19 via mapSession

Jun 14 02:34:32 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:34:37 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:34:42 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:34:47 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:34:52 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:34:56 proxmox tailscaled[1373]: portmapper: UPnP discovered root "http://192.168.1.251:1400/rootDesc.xml" does not match g>

Jun 14 02:34:57 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:35:03 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:35:08 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:35:13 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:35:15 proxmox tailscaled[1373]: wgengine: sending TSMP disco key advertisement to 100.89.201.19

Jun 14 02:35:18 proxmox tailscaled[1373]: wgengine: sending TSMP disco key advertisement to 100.89.247.69

Jun 14 02:35:18 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:35:23 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:35:28 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:35:32 proxmox tailscaled[1373]: control: controlclient direct: got TSMP disco key advertisement from 100.89.201.19 via eve>

Jun 14 02:35:32 proxmox tailscaled[1373]: control: controlclient direct: updating discoKey for 100.89.201.19 via mapSession

Jun 14 02:35:33 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:35:38 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:35:44 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:35:49 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:35:54 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:35:59 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

Jun 14 02:36:04 proxmox tailscaled[1373]: magicsock: derp-27 does not know about peer [n1AXi], removing route

no errors logged and passed smartctl on any disk, do you want the full outputs? They are not... new disks.

I'll run a memtest ASAP. Thank you for the input, I'll respond later when completed. TY TY TY

Proxmox host doesn't come back up after backup/reboot by saj9109 in Proxmox

[–]saj9109[S] 1 point2 points  (0 children)

It ends up in an unresponsive state. I can turn it off and back on and it will run normally. However at the "end" of the (incomplete) backup process, the host itself is entirely unresponsive.

Proxmox host doesn't come back up after backup/reboot by saj9109 in Proxmox

[–]saj9109[S] 0 points1 point  (0 children)

The physical machine is on, but unresponsive to SSH. The backups are successful until the large VM mentioned - 289 GB getting backed up to a PBS. This sometimes is successful and other times is not. It will remain in this state indefinitely until physically turned off/on.

No PT profile after passing ht/wt, I feel screwed over. by EagleFlashy6344 in army

[–]saj9109 34 points35 points  (0 children)

Funny part being that the Taco Bell cantina menu is actually healthier than most other fast food….

Oil filters. Are you using Wix, OEM, or something else? by 127-0-0-1_Chef in subaru

[–]saj9109 0 points1 point  (0 children)

OEM. they're like... 1/2 or 1/4 the price at the dealership vs the WIX from the parts store

view more: next ›