Search results

Ok, thanks a bunch..i'll now try to upgrade. The error is gone when i run pve6to7

Hello, i'm trying to upgrade from ver 6 to 7. After checking via pve6to7 i get the error: INFO: Checking if resolved IP is configured on local node.. FAIL: Resolved node IP '192.168.178.106' not configured or active for 'pve' The IP of my proxmox is 192.168.178.10. There is no VM or container...

Thanks! it was in the etc/resolv.conf file set to the pihole DNS. But, i wonder why? I don't recall doing that. I've set it back to the router as DNS and all works. Thanks again.

Hello, i'm not a proxmox or linux expert, so forgive the question if it is too simple. I have a proxmox machine running 6.4-15, and wanted to upgrade to ver 7. In doing so i had to shut down all VM's. One of these VM's is pihole for my network, which is working fine for the clients on the...

Here the output of the ip a and r root@pve:~# ip a 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6...

It reads like it's all ok, but not sure. I'm not sure I understand the concept of the network interfaces....the hardware one is enp3s0...and i'm guessing the vmbr0 is a virtualized one? Also, i'd like to get the wlan working also...but not sure how...

Hello, it now is working fine, all of a sudden, i did nothing. I just entered the link again and all of a sudden, after entering the link 20 times, it worked. Here is the interfaces: auto lo iface lo inet loopback iface enp3s0 inet manual auto vmbr0 iface vmbr0 inet static address...

Hello, i've had a few proxmox installations, all working fine. Recently my proxmos server has a problem, very strange. The VM's on the server are working fine and i can reach them on the network. But, i can no longer reach the proxmox server itself on the network. It has disappeared. So, i've...

Hallo, ich denke das waere das beste. Danke!

Habe ein bisschen herumgesucht und gefunden wo motion.log ist, bzw. sein sollte...ist da, aber lehr ?? root@MotioneyeProx:/var/log# pwd /var/log root@MotioneyeProx:/var/log# ls -l total 17432 -rw-r--r-- 1 root root 18036 Mar 19 21:25 alternatives.log drwxr-xr-x 2 root root 4096 Mar 21 09:24...

Hi, also anscheinend soll die configdatei in diesem /data/etc sein...aber da ist ja nichts, und der path hatte vorher nicht existiert. conf_path /data/etc run_path /tmp log_path /var/log media_path /data/output motion_binary /usr/bin/motion log_level info listen 0.0.0.0 port 80...

Hi, habe ich gemacht, macht aber keinen Unterschied. Ja, der Ordner ist leer. Aber Motioneye hatte zuerst funktioniert, hatte also diesen Ordner nicht am Anfang gebraucht?

Hi, unten ist was steht dabei: Das kann ich nicht so erkennen...Sorry, bin ein bisschen Laie, probiere zu lernen.. root@MotioneyeProx:/data# cat /etc/passwd root:x:0:0:root:/root:/bin/bash daemon:x:1:1:daemon:/usr/sbin:/usr/sbin/nologin bin:x:2:2:bin:/bin:/usr/sbin/nologin...

Hallo, ich weiß leider nicht wie ich das überprüfen kann, aber ich denk mal ja, da es kein anderes Konto auf dem container gibt.

Hallo, danke fuer die HIlfe. Nein, der Ordner war nicht da, habe ihn jetzt kreiert, aber motioneye startet trotzdem nicht. Hier die Order Permissions: root@MotioneyeProx:/data# ls -l total 8 drwxr-xr-x 2 root root 4096 Mar 20 21:21 etc drwxr-xr-x 7 root root 4096 Mar 20 00:22 output

Hallo, habe ein mitioneye container der nach reboot nicht mehr startet. Vor dem reboot hat er gut funktioniert. Ist auf Debian basis, hier der output von systemctl kann mir jemand helfen? dake. root@MotioneyeProx:~# systemctl status motioneye.service * motioneye.service - motionEye Server...

Hello, sorry but I need to open this old thread again, but I'm still having this same problem for containers. I've changed the permissions mapping as noted above, but no luck. The backup stops due to lacking priveledge. Is there a workaround somehow? thanks