Recent content by SimonMcNair

I recently upgraded from Bookworm to Trixie and I didn't think that replacing my sshd_config with the distribution release would cause a conflict (naive I know, and yes, it probably said in the documentation not to replace it but I assumed ciphers would be updated etc). Then I came across this...

I'm finding that one of my cluster nodes appears greyed out every so often since upgrading from bookworm to Trixie. I need to try earlier kernel versions but just wondered if anyone else has come across it ? When I look on the console the machine is up and running. proxmox-ve: 9.0.0 (running...

I don't think this is Proxmox or Influx. I think it's telegraf, but I don't know why. I will gather evidence. Thanks for your help.

Seems like I'm not the only one. Kinda confused as to why it is happening, maybe the error is a misnomer https://community.influxdata.com/t/influxdb2-telegraf-proxmox-field-type-conflict-while-using-inputs-socket-listener-for-proxmox-metrics/23585

I'd love to know how to do this. It's beyond my linux foo at the moment

--- version: '3.8' services: app: image: 'jc21/nginx-proxy-manager:latest' container_name: npm restart: unless-stopped ports: - '80:80' # Public HTTP Port - '443:443' # Public HTTPS Port - '81:81' # Admin Web Port volumes: - ./data:/data -...

When I run telegraf --test /etc/telegraf the output for system is: > system,host=134e7e15f4ba load1=2.21,load15=1.92,load5=2.31,n_cpus=1i,n_users=0i 1667813275000000000 > system,host=134e7e15f4ba uptime=245239i 1667813275000000000 > system,host=134e7e15f4ba uptime_format="2 days, 20:07"...

Thank you for taking the time to check the code and confirm it isn't proxmox. Considering The only two sources I have writing to the influxdb are proxmox and telegraf I'm confused as to what could have created the metric as a float. I will investigate further. Thanks again.

Hi, I happened to look at my influx logs and noticed the following error occurring: ts=2022-11-03T15:52:15.241668Z lvl=info msg="Failed to write point batch to database" log_id=0dwTt70G000 service=udp db_instance=udp error="partial write: field type conflict: input field \"uptime\" on...

with mine this happens when my session is stale and/or I'm logging on to another node in the cluster from a logon session on a different server. normally just refreshing the page and logging in again fixes it. Not saying that's the answer, just that I've seen it before.

nope ? No-one ?

I use docker with jc21/nginx-proxy-manager on a separate VM. Easy as pie and just as tasty. Willing to accept other methods work just as well though.

Hi, Given the changes that proxmox makes to grub running does anyone know the process to add more entries to the grub menu please ? I tried grml-rescue to no avail. Your help would be appreciated.

I think, but am not sure, that lxc provides a certain level of isolation, but not as much as a vm. If you run docker in lxc some containers may not work if they require access to the kernel that lxc will not permit ? If someone could clarify or correct me I would appreciate it.

From what I can see the bgp one appears more superior in all ways, but I haven't used it