NEWS
Test Adapter ioBroker.backitup v3.0.x
-
@simatec mal eine "unverschämte" Frage. Da ich seit kurzem eine PV Anlage mit Speicher + Wallbox habe, nutze ich für die Speicherung der Werte eine influxdb und zur grafischen Anzeige Grafana. Das läuft auch prima mit iobroker zusammen.
Es wäre toll wenn ich zur Sicherung auch den backitup Adapter nutzen könnte
Backup für influxdb ist eigentlich ganz einfach:
sudo influxd backup -portable /opt/backups/influx.backup
restore auch
influxd restore -portable /opt/backups/influx.backup
für Grafana ist es komplizierter (siehe: https://www.bachmann-lan.de/grafana-backup-dashboards-data-sources/)
Momentan starte ich zwei scripte über die shell.
Ob man das "irgendwann mal" in den Backitup Adapter aufnehmen könnte ? -
@HAL
Ist mit auf der Todo ... -
Super cooler Adapter, der mir schon einige Male den Hintern gerettet hat! Danke!
beim gestrigen Schrotten meines iobroker rasp pi ist beim Zurückspielen auf die frische Installation folgender Fehler aufgetreten:
DEBUG] [redis] Start Redis Restore ... [DEBUG] [redis] Created Redis tmp [ERROR] [redis] Redis Restore not completed [ERROR] [redis] Error: EPERM: operation not permitted, utime '/opt/iobroker/backups/tmp/' [EXIT] undefined **** Restore completed successfully!! **** The log can be closed ...
Der Restore von Iobroker selbst hat funktioniert... nur eben Redis nicht. Auch die fehlenden Werte in den Objekten (und die sehr kleinen Redis-Backups nach diesem restore) deuten darauf hin dass das Zurückspielen nicht funktioniert hat.
Habe die frische Installation zuvor auf Redis umgestellt und Redis vorher installiert.
Dann habe ich auchsudo usermod -a -G redis iobroker
und zur Vorsicht noch
curl -fsL https://iobroker.net/fix.sh | bash -
sowie zwischendurch immer reboots durchgeführt. So langsam komme ich mit meinen begrenzten Mitteln nicht weiter. Hat jemand eine Idee?
VG
Tobiupdate:
ich habe mal diesen ordner /opt/iobroker/backups/tmp als root mit 0777 angelegt -> selbe Fehlermeldung und nachdem Redis-Restore-Versuch ist der wieder weg.
-
@tobitobsta sagte in Test Adapter Backitup v1.7.x:
ich habe mal diesen ordner /opt/iobroker/backups/tmp als root mit 0777 angelegt
Ganz schlechte Idee...
Im Normalzustand gibt es den Ordner auf meinem System auch gar nicht. Vermutlich wird der während des Backups wirklich nur temporär angelegt.
Was jetzt aber da konkret bei dir falsch / anders läuft kann ich nur raten.Apropos raten: Ich würde dir raten, dich nicht als root anzmelden und dann in den Verzeichnispfaden rumzufummeln.
Dateisystem ist aber gesund?
Mitdmesg
mal schauen.
Die user sind in den passenden Gruppen?sudo -u iobroker groups groups
-
@Thomas-Braun
Danke für den Hinweis bzgl root und Verzeichnisstrukturen.Dateisystem sieht erstmal okay aus.
iobroker befindet sich auch in der redis-gruppe. Der user "pi" jedoch nicht - müsste er das? Denke iobroker sollte reichen.leider kann ich aus dem redis log auch nichts rauslesen - zumindest sieht es da nicht nach einem abgelehnten zugriffsversuch aus.
-
@tobitobsta Poste doch mal bitte die Ausgaben der Befehle.
-
@Thomas-Braun
here we go (dmesg):[ 0.872784] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 249) [ 0.873037] io scheduler mq-deadline registered [ 0.873066] io scheduler kyber registered [ 0.877118] brcm-pcie fd500000.pcie: host bridge /scb/pcie@7d500000 ranges: [ 0.877163] brcm-pcie fd500000.pcie: No bus range found for /scb/pcie@7d500000, using [bus 00-ff] [ 0.877268] brcm-pcie fd500000.pcie: MEM 0x0600000000..0x0603ffffff -> 0x00f8000000 [ 0.877359] brcm-pcie fd500000.pcie: IB MEM 0x0000000000..0x00bfffffff -> 0x0000000000 [ 0.936694] brcm-pcie fd500000.pcie: link up, 5 GT/s x1 (SSC) [ 0.937034] brcm-pcie fd500000.pcie: PCI host bridge to bus 0000:00 [ 0.937069] pci_bus 0000:00: root bus resource [bus 00-ff] [ 0.937103] pci_bus 0000:00: root bus resource [mem 0x600000000-0x603ffffff] (bus address [0xf8000000-0xfbffffff]) [ 0.937183] pci 0000:00:00.0: [14e4:2711] type 01 class 0x060400 [ 0.937467] pci 0000:00:00.0: PME# supported from D0 D3hot [ 0.940741] PCI: bus0: Fast back to back transfers disabled [ 0.940990] pci 0000:01:00.0: [1106:3483] type 00 class 0x0c0330 [ 0.941153] pci 0000:01:00.0: reg 0x10: [mem 0x00000000-0x00000fff 64bit] [ 0.941602] pci 0000:01:00.0: PME# supported from D0 D3cold [ 0.944910] PCI: bus1: Fast back to back transfers disabled [ 0.944986] pci 0000:00:00.0: BAR 8: assigned [mem 0x600000000-0x6000fffff] [ 0.945024] pci 0000:01:00.0: BAR 0: assigned [mem 0x600000000-0x600000fff 64bit] [ 0.945125] pci 0000:00:00.0: PCI bridge to [bus 01] [ 0.945164] pci 0000:00:00.0: bridge window [mem 0x600000000-0x6000fffff] [ 0.945492] pcieport 0000:00:00.0: enabling device (0140 -> 0142) [ 0.945754] pcieport 0000:00:00.0: PME: Signaling with IRQ 55 [ 0.946174] pcieport 0000:00:00.0: AER: enabled with IRQ 55 [ 0.946534] pci 0000:01:00.0: enabling device (0140 -> 0142) [ 0.953506] iproc-rng200 fe104000.rng: hwrng registered [ 0.953858] vc-mem: phys_addr:0x00000000 mem_base=0x3ec00000 mem_size:0x40000000(1024 MiB) [ 0.954521] vc-sm: Videocore shared memory driver [ 0.955174] gpiomem-bcm2835 fe200000.gpiomem: Initialised: Registers at 0xfe200000 [ 0.967382] brd: module loaded [ 0.979746] loop: module loaded [ 0.981183] Loading iSCSI transport class v2.0-870. [ 0.983154] libphy: Fixed MDIO Bus: probed [ 0.983801] bcmgenet fd580000.ethernet: failed to get enet clock [ 0.983837] bcmgenet fd580000.ethernet: GENET 5.0 EPHY: 0x0000 [ 0.983875] bcmgenet fd580000.ethernet: failed to get enet-wol clock [ 0.983911] bcmgenet fd580000.ethernet: failed to get enet-eee clock [ 0.983954] bcmgenet: Skipping UMAC reset [ 0.994628] libphy: bcmgenet MII bus: probed [ 1.084660] unimac-mdio unimac-mdio.-19: Broadcom UniMAC MDIO bus [ 1.085698] usbcore: registered new interface driver r8152 [ 1.085779] usbcore: registered new interface driver lan78xx [ 1.085853] usbcore: registered new interface driver smsc95xx [ 1.086309] xhci_hcd 0000:01:00.0: xHCI Host Controller [ 1.086358] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 1 [ 1.088980] xhci_hcd 0000:01:00.0: hcc params 0x002841eb hci version 0x100 quirks 0x0000001000000890 [ 1.090301] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002, bcdDevice= 5.04 [ 1.090340] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.090375] usb usb1: Product: xHCI Host Controller [ 1.090403] usb usb1: Manufacturer: Linux 5.4.72-v7l+ xhci-hcd [ 1.090432] usb usb1: SerialNumber: 0000:01:00.0 [ 1.091051] hub 1-0:1.0: USB hub found [ 1.091175] hub 1-0:1.0: 1 port detected [ 1.091773] xhci_hcd 0000:01:00.0: xHCI Host Controller [ 1.091815] xhci_hcd 0000:01:00.0: new USB bus registered, assigned bus number 2 [ 1.091857] xhci_hcd 0000:01:00.0: Host supports USB 3.0 SuperSpeed [ 1.092403] usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.04 [ 1.092442] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [ 1.092476] usb usb2: Product: xHCI Host Controller [ 1.092505] usb usb2: Manufacturer: Linux 5.4.72-v7l+ xhci-hcd [ 1.092534] usb usb2: SerialNumber: 0000:01:00.0 [ 1.093132] hub 2-0:1.0: USB hub found [ 1.093248] hub 2-0:1.0: 4 ports detected [ 1.094789] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [ 1.095098] dwc_otg: FIQ enabled [ 1.095111] dwc_otg: NAK holdoff enabled [ 1.095123] dwc_otg: FIQ split-transaction FSM enabled [ 1.095139] Module dwc_common_port init [ 1.095581] usbcore: registered new interface driver uas [ 1.095704] usbcore: registered new interface driver usb-storage [ 1.095912] mousedev: PS/2 mouse device common for all mice [ 1.097794] bcm2835-wdt bcm2835-wdt: Broadcom BCM2835 watchdog timer [ 1.101249] sdhci: Secure Digital Host Controller Interface driver [ 1.101281] sdhci: Copyright(c) Pierre Ossman [ 1.101909] mmc-bcm2835 fe300000.mmcnr: could not get clk, deferring probe [ 1.102495] sdhci-pltfm: SDHCI platform and OF driver helper [ 1.106361] ledtrig-cpu: registered to indicate activity on CPUs [ 1.106691] hidraw: raw HID events driver (C) Jiri Kosina [ 1.106903] usbcore: registered new interface driver usbhid [ 1.106931] usbhid: USB HID core driver [ 1.107978] vchiq: vchiq_init_state: slot_zero = (ptrval) [ 1.111604] [vc_sm_connected_init]: start [ 1.120598] [vc_sm_connected_init]: end - returning 0 [ 1.122844] Initializing XFRM netlink socket [ 1.122898] NET: Registered protocol family 17 [ 1.123030] Key type dns_resolver registered [ 1.123414] Registering SWP/SWPB emulation handler [ 1.123733] registered taskstats version 1 [ 1.123766] Loading compiled-in X.509 certificates [ 1.124310] Key type ._fscrypt registered [ 1.124338] Key type .fscrypt registered [ 1.135099] uart-pl011 fe201000.serial: cts_event_workaround enabled [ 1.135193] fe201000.serial: ttyAMA0 at MMIO 0xfe201000 (irq = 29, base_baud = 0) is a PL011 rev2 [ 1.141319] bcm2835-power bcm2835-power: Broadcom BCM2835 power domains driver [ 1.142324] mmc-bcm2835 fe300000.mmcnr: mmc_debug:0 mmc_debug2:0 [ 1.142356] mmc-bcm2835 fe300000.mmcnr: DMA channel allocated [ 1.194371] mmc1: queuing unknown CIS tuple 0x80 (2 bytes) [ 1.196125] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 1.197983] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 1.201000] mmc1: queuing unknown CIS tuple 0x80 (7 bytes) [ 1.202690] mmc1: queuing unknown CIS tuple 0x80 (3 bytes) [ 1.209837] mmc0: SDHCI controller on fe340000.emmc2 [fe340000.emmc2] using ADMA [ 1.213028] of_cfs_init [ 1.213159] of_cfs_init: OK [ 1.214435] Waiting for root device PARTUUID=7482b1ce-02... [ 1.253748] random: fast init done [ 1.287420] mmc1: new high speed SDIO card at address 0001 [ 1.320454] mmc0: new ultra high speed DDR50 SDHC card at address aaaa [ 1.321388] mmcblk0: mmc0:aaaa SH32G 29.7 GiB [ 1.323765] mmcblk0: p1 p2 [ 1.345587] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [ 1.345677] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [ 1.351019] devtmpfs: mounted [ 1.359759] Freeing unused kernel memory: 2048K [ 1.374863] Run /sbin/init as init process [ 1.454614] usb 1-1: new high-speed USB device number 2 using xhci_hcd [ 1.637382] usb 1-1: New USB device found, idVendor=2109, idProduct=3431, bcdDevice= 4.21 [ 1.637426] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0 [ 1.637458] usb 1-1: Product: USB2.0 Hub [ 1.639630] hub 1-1:1.0: USB hub found [ 1.639915] hub 1-1:1.0: 4 ports detected [ 1.815053] systemd[1]: System time before build time, advancing clock. [ 1.912629] NET: Registered protocol family 10 [ 1.914054] Segment Routing with IPv6 [ 1.943043] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 default-hierarchy=hybrid) [ 1.943863] systemd[1]: Detected architecture arm. [ 1.964604] usb 1-1.3: new full-speed USB device number 3 using xhci_hcd [ 2.034737] systemd[1]: Set hostname to <iobroker>. [ 2.105077] usb 1-1.3: New USB device found, idVendor=0451, idProduct=16a8, bcdDevice= 0.09 [ 2.105125] usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 2.105161] usb 1-1.3: Product: TI CC2531 USB CDC [ 2.105190] usb 1-1.3: Manufacturer: Texas Instruments [ 2.105219] usb 1-1.3: SerialNumber: __0X00124B000BE8A20E [ 2.707077] random: systemd: uninitialized urandom read (16 bytes read) [ 2.721301] random: systemd: uninitialized urandom read (16 bytes read) [ 2.721858] systemd[1]: Listening on udev Kernel Socket. [ 2.722800] random: systemd: uninitialized urandom read (16 bytes read) [ 2.728270] systemd[1]: Listening on Syslog Socket. [ 2.731895] systemd[1]: Created slice system-systemd\x2dfsck.slice. [ 2.732758] systemd[1]: Listening on initctl Compatibility Named Pipe. [ 2.733855] systemd[1]: Listening on fsck to fsckd communication Socket. [ 2.734760] systemd[1]: Started Forward Password Requests to Wall Directory Watch. [ 2.736088] systemd[1]: Listening on Journal Socket. [ 3.365389] EXT4-fs (mmcblk0p2): re-mounted. Opts: (null) [ 3.457918] systemd-journald[113]: Received request to flush runtime journal from PID 1 [ 3.966447] rpivid-mem feb00000.hevc-decoder: rpivid-hevcmem initialised: Registers at 0xfeb00000 length 0x00010000 [ 3.966956] rpivid-mem feb10000.rpivid-local-intc: rpivid-intcmem initialised: Registers at 0xfeb10000 length 0x00001000 [ 3.970164] rpivid-mem feb20000.h264-decoder: rpivid-h264mem initialised: Registers at 0xfeb20000 length 0x00010000 [ 3.976805] rpivid-mem feb30000.vp9-decoder: rpivid-vp9mem initialised: Registers at 0xfeb30000 length 0x00010000 [ 4.107110] vc_sm_cma: module is from the staging directory, the quality is unknown, you have been warned. [ 4.107282] snd_bcm2835: module is from the staging directory, the quality is unknown, you have been warned. [ 4.111882] bcm2835_vc_sm_cma_probe: Videocore shared memory driver [ 4.111908] [vc_sm_connected_init]: start [ 4.117593] [vc_sm_connected_init]: installed successfully [ 4.134353] mc: Linux media interface: v0.10 [ 4.194400] bcm2835_audio bcm2835_audio: card created with 8 channels [ 4.200184] videodev: Linux video capture interface: v2.00 [ 4.265102] bcm2835_mmal_vchiq: module is from the staging directory, the quality is unknown, you have been warned. [ 4.270376] bcm2835_isp: module is from the staging directory, the quality is unknown, you have been warned. [ 4.285473] bcm2835-isp bcm2835-isp: Device node output[0] registered as /dev/video13 [ 4.289686] bcm2835-isp bcm2835-isp: Device node capture[0] registered as /dev/video14 [ 4.292951] bcm2835-isp bcm2835-isp: Device node capture[1] registered as /dev/video15 [ 4.293715] bcm2835-isp bcm2835-isp: Device node stats[2] registered as /dev/video16 [ 4.293751] bcm2835-isp bcm2835-isp: Register output node 0 with media controller [ 4.293775] bcm2835-isp bcm2835-isp: Register capture node 1 with media controller [ 4.293821] bcm2835-isp bcm2835-isp: Register capture node 2 with media controller [ 4.293842] bcm2835-isp bcm2835-isp: Register capture node 3 with media controller [ 4.293847] bcm2835_v4l2: module is from the staging directory, the quality is unknown, you have been warned. [ 4.294064] bcm2835-isp bcm2835-isp: Loaded V4L2 bcm2835-isp [ 4.349366] cfg80211: Loading compiled-in X.509 certificates for regulatory database [ 4.352132] bcm2835_codec: module is from the staging directory, the quality is unknown, you have been warned. [ 4.370527] bcm2835-codec bcm2835-codec: Device registered as /dev/video10 [ 4.370572] bcm2835-codec bcm2835-codec: Loaded V4L2 decode [ 4.387377] bcm2835-codec bcm2835-codec: Device registered as /dev/video11 [ 4.387420] bcm2835-codec bcm2835-codec: Loaded V4L2 encode [ 4.427223] bcm2835-codec bcm2835-codec: Device registered as /dev/video12 [ 4.427266] bcm2835-codec bcm2835-codec: Loaded V4L2 isp [ 4.497829] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' [ 4.508478] [drm] Initialized v3d 1.0.0 20180419 for fec00000.v3d on minor 0 [ 4.593744] brcmfmac: F1 signature read @0x18000000=0x15264345 [ 4.611429] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 4.611868] usbcore: registered new interface driver brcmfmac [ 4.635275] brcmfmac mmc1:0001:1: Direct firmware load for brcm/brcmfmac43455-sdio.raspberrypi,4-model-b.txt failed with error -2 [ 4.666016] [drm] No displays found. Consider forcing hotplug if HDMI is attached [ 4.666506] vc4-drm gpu: bound fe600000.firmwarekms (ops vc4_fkms_ops [vc4]) [ 4.666559] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). [ 4.666591] [drm] No driver support for vblank timestamp query. [ 4.666623] [drm] Setting vblank_disable_immediate to false because get_vblank_timestamp == NULL [ 4.682271] [drm] Initialized vc4 0.0.0 20140616 for gpu on minor 1 [ 4.721812] cdc_acm 1-1.3:1.0: ttyACM0: USB ACM device [ 4.725955] usbcore: registered new interface driver cdc_acm [ 4.726028] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters [ 4.872041] brcmfmac: brcmf_fw_alloc_request: using brcm/brcmfmac43455-sdio for chip BCM4345/6 [ 4.887639] brcmfmac: brcmf_c_preinit_dcmds: Firmware: BCM4345/6 wl0: Mar 23 2020 02:19:54 version 7.45.206 (r725000 CY) FWID 01-88ee44ea [ 6.649834] uart-pl011 fe201000.serial: no DMA platform data [ 6.793534] 8021q: 802.1Q VLAN Support v1.8 [ 6.833530] random: crng init done [ 6.833547] random: 7 urandom warning(s) missed due to ratelimiting [ 7.004588] Adding 102396k swap on /var/swap. Priority:-2 extents:2 across:307200k SSFS [ 7.231550] bcmgenet: Skipping UMAC reset [ 7.233099] bcmgenet fd580000.ethernet: configuring instance for external RGMII [ 7.233291] bcmgenet fd580000.ethernet eth0: Link is Down [ 12.394731] bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx [ 12.394778] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 13.390194] Bluetooth: Core ver 2.22 [ 13.390278] NET: Registered protocol family 31 [ 13.390292] Bluetooth: HCI device and connection manager initialized [ 13.390319] Bluetooth: HCI socket layer initialized [ 13.390339] Bluetooth: L2CAP socket layer initialized [ 13.390370] Bluetooth: SCO socket layer initialized [ 13.400185] Bluetooth: HCI UART driver ver 2.3 [ 13.400204] Bluetooth: HCI UART protocol H4 registered [ 13.400291] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 13.400609] Bluetooth: HCI UART protocol Broadcom registered [ 13.645614] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 13.645624] Bluetooth: BNEP filters: protocol multicast [ 13.645637] Bluetooth: BNEP socket layer initialized [ 13.677962] ICMPv6: process `dhcpcd' is using deprecated sysctl (syscall) net.ipv6.neigh.eth0.retrans_time - use net.ipv6.neigh.eth0.retrans_time_ms instead [ 36.486035] FS-Cache: Netfs 'cifs' registered for caching [ 36.494244] Key type cifs.spnego registered [ 36.494260] Key type cifs.idmap registered [ 36.497493] CIFS: Attempting to mount //server/tobi/Backup/iobroker [ 179.685049] CIFS: Attempting to mount //server/tobi/Backup/iobroker [ 211.740935] CIFS: Attempting to mount //server/tobi/Backup/iobroker [ 211.794216] CIFS: Attempting to mount //server/tobi/Backup/iobroker [ 211.794274] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [ 2926.815460] CIFS: Attempting to mount //server/tobi/Backup/iobroker [ 3049.571700] CIFS: Attempting to mount //server/tobi/Backup/iobroker [ 3083.871685] CIFS: Attempting to mount //server/tobi/Backup/iobroker [ 3083.946733] CIFS: Attempting to mount //server/tobi/Backup/iobroker [ 3083.946792] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [ 4364.779967] CIFS: Attempting to mount //server/tobi/Backup/iobroker [ 4396.513037] CIFS: Attempting to mount //server/tobi/Backup/iobroker [ 4396.585580] CIFS: Attempting to mount //server/tobi/Backup/iobroker [ 4396.585637] No dialect specified on mount. Default has changed to a more secure dialect, SMB2.1 or later (e.g. SMB3), from CIFS (SMB1). To use the less secure SMB1 dialect to access old servers which do not support SMB3 (or SMB2.1) specify vers=1.0 on mount. [ 4618.763633] CIFS: Attempting to mount //server/tobi/Backup/iobroker [ 9755.613491] CIFS: Attempting to mount //server/tobi/Backup/iobroker
pi@iobroker: sudo -u iobroker groups iobroker tty dialout audio video bluetooth redis gpio i2c
pi@iobroker:/opt/iobroker $ groups pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi iobroker
-
@tobitobsta sagte in Test Adapter Backitup v1.7.x:
CIFS: Attempting to mount //server/tobi/Backup/iobroker
Du hättest ja auch mal verkünden können, das das ein gemountetes Dateisystem an der Stelle ist.
Wie sehen die mount-Optionen aus? -
@Thomas-Braun ja das hätte ich tun können...
"connectType": "CIFS", "cifsMount": "*****", "cifsDomain": "", "cifsUser": "******", "cifsPassword": "******", "smbType": "vers=3.0", "sudoMount": true, "cifsDeleteOldBackup": false, "cifsOwnDir": false, "wakeOnLAN": true,
mounting scheint zumindest so weit zu funktionieren, dass ich die backups in der Auswahlliste sehe. Und acuh das Backup erstellen funktioniert auf dem mount ohne Probleme.
-
@tobitobsta
Mache mal bitte den Restore Lokal. Cloud und NAS ist immer nicht so das Gelbe vom Ei .... -
@tobitobsta
Wird über die fstab gemounted?
Dann bitte die dortigen Einträge nennen.
Ansonsten das was @simatec sagt. -
@Thomas-Braun mounting passiert über den Adapter
@simatec vielen Dank für den Hinweis. So funktioniert es dann. Dann verstehe ich zwar noch nicht warum das auf dem alten System ohne weiteres ging - aber erstmal bin ich natürlich glücklich das es so geht. Danke Dir!!!
Was ich noch nicht verstehe ist, dass mein Redis-Backup, was ich drauf spiele, ca 3.7MB groß ist und nach einem Zurückspielen und erneutem Backup das Redis-Backup nur noch 650KB groß ist. Aber wie ihr ja bereits merkt - meine Mittel sind begrenzt
-
@tobitobsta
Prüfe mal die Rechte auf deinem NAS. So wie es aussieht, hat iobroker bzw. Backitup keine Schreibrechte -
Hallo zusammen,
seit 2 Tagen werden keine iobroker Archive mehr in mein NAS Drive geschrieben.
Pushover sagt immer erfolgreich im VIS HTML steht aber immer name undefined.redis und zigbee.0 kommen an und werden auch geschrieben.
Ich habe jetzt backitup mit debug laufen lassen und hänge mal das Log mit an.
Ebenso das log wenn ich den Adapter zum backuppen händisch starte.Vielleicht gibt es ja einen Tip von Euch
vielen Dank
Backitup2.txt Backitup1.txt -
@simatec Aber dann könnte er ja das Backup auch dort nicht erstellen - aber das geht ja wunderbar. Oder er hängt es beim Backup "anders" ein als beim Wiederherstellen... Aber ich Denke im Grunde hast Du recht: Es scheint ein Rechte-Problem zu sein. Der Mount Befehl für die Wiederherstellung im log sieht für mich jetzt auch okay aus:
sudo mount -t cifs -o username=tobi,password=****,rw,file_mode=0777,dir_mode=0777 //server/tobi/Backup/iobroker /opt/iobroker/backups
Unterschied: der Ordner "backups" gehört vor dem mounten user iobroker - nachdem mounten "root" - aber er ist tatsächlich 0777 Rechten versehen.
-
@HAL
Wenn du Influxdb mal testen willst, kannst du gerne mal die DEV Version testen.
Im Moment geht noch kein Restore -
@simatec
Mal sehen ob übermorgen ( morgen bin ich unterwegs ) auf meinen NAS etwas zu finden ist.Manuell kann man den Backup aber nicht anstoßen, korrekt ?
-
@HAL
Nein ... es wird als Option wie die anderen Datenbanken bei einem iobroker Backup mit ausgeführt -
Guten Morgen,
ich habe hier einige Error im Log. Sicherung startet täglich um 2Uhr und soll die IoBroker sowie Zigbee Daten in Google Drive sichern.
Iobroker läuft auf einem NUC unter Proxmox mit Ubuntu Server
Node.js v10.22.0
NPM 6.14.6Systeminfos
iobroker_server Platform linux Betriebssystem linux Architektur x64 CPUs 1 Geschwindigkeit 2165 MHz Modell Common KVM processor RAM 3.85 GB System Betriebszeit 1 T. 20:30:01 Node.js v10.22.0 (Es gibt eine neuere Version: v10.23.0 - Empfohlene Version v12.19.1) NPM 6.14.6 Festplatte Größe 15.64 GB Festplatte frei 8.32 GB Anzahl der Adapter 312 Betriebszeit 1 T. 20:29:37 Aktive Instanzen 15 Hostname iobroker_server
Log
2020-11-18 02:00:10.045 - debug: backitup.0 (4228) Backup has started ... 2020-11-18 02:00:12.693 - info: ical.0 (6395) processing URL: XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 2020-11-18 02:00:16.600 - debug: backitup.0 (4228) [iobroker/iobroker] host.iobroker_server 5248 states saved 2020-11-18 02:00:16.664 - debug: backitup.0 (4228) [iobroker/iobroker] host.iobroker_server 3577 objects saved 2020-11-18 02:00:18.420 - warn: host.iobroker_server Objects 127.0.0.1:45828 Error from InMemDB: Error: ERROR readDir id=0_userdata.0: Not exists 2020-11-18 02:00:18.421 - warn: host.iobroker_server Objects 127.0.0.1:45828 Error from InMemDB: Error: ERROR readDir id=admin.0: Not exists 2020-11-18 02:00:18.427 - warn: readFile will not read this file (css/vis-common-user.css) in future versions: vis is not an object of type "meta" 2020-11-18 02:00:18.428 - warn: host.iobroker_server Objects 127.0.0.1:45828 Error from InMemDB: Error: ERROR readDir id=web.0: Not exists 2020-11-18 02:00:19.868 - info: ical.0 (6395) Terminated (NO_ERROR): Without reason 2020-11-18 02:00:20.409 - info: host.iobroker_server instance system.adapter.ical.0 terminated with code 0 (NO_ERROR) 2020-11-18 02:00:22.336 - debug: backitup.0 (4228) [iobroker/iobroker] Backup created: /opt/iobroker/backups/iobroker_2020_11_18-02_00_10_backupiobroker.tar.gz 2020-11-18 02:00:23.388 - debug: backitup.0 (4228) [iobroker/iobroker] done 2020-11-18 02:00:23.992 - debug: backitup.0 (4228) [iobroker/zigbee] found zigbee database: zigbee.0 2020-11-18 02:00:23.993 - debug: backitup.0 (4228) [iobroker/zigbee] done 2020-11-18 02:00:24.445 - debug: backitup.0 (4228) [iobroker/googledrive] Google Drive: Copy iobroker_2020_11_18-02_00_10_backupiobroker.tar.gz... 2020-11-18 02:00:24.460 - debug: backitup.0 (4228) [iobroker/clean] delete /opt/iobroker/backups/iobroker_2020_11_14-02_00_10_backupiobroker.tar.gz 2020-11-18 02:00:24.461 - debug: backitup.0 (4228) [iobroker/clean] delete /opt/iobroker/backups/iobroker_2020_11_13-02_00_10_backupiobroker.tar.gz 2020-11-18 02:00:24.465 - debug: backitup.0 (4228) [iobroker/clean] delete /opt/iobroker/backups/zigbee.0_2020_11_14-02_00_22_backupiobroker.tar.gz 2020-11-18 02:00:24.466 - debug: backitup.0 (4228) [iobroker/clean] delete /opt/iobroker/backups/zigbee.0_2020_11_13-02_00_22_backupiobroker.tar.gz 2020-11-18 02:00:24.467 - debug: backitup.0 (4228) [iobroker/clean] done 2020-11-18 02:00:24.968 - error: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). 2020-11-18 02:00:24.969 - error: backitup.0 (4228) unhandled promise rejection: Rate Limit Exceeded 2020-11-18 02:00:25.054 - error: backitup.0 (4228) Error: Rate Limit Exceeded at Gaxios._request (/opt/iobroker/node_modules/gaxios/src/gaxios.ts:112:15) at process._tickCallback (internal/process/next_tick.js:68:7) 2020-11-18 02:00:25.055 - info: backitup.0 (4228) cleaned everything up... 2020-11-18 02:00:25.121 - info: backitup.0 (4228) terminating 2020-11-18 02:00:25.122 - debug: backitup.0 (4228) Plugin sentry destroyed 2020-11-18 02:00:25.123 - info: backitup.0 (4228) Terminated (NO_ERROR): Without reason 2020-11-18 02:00:25.283 - debug: backitup.0 (4228) [iobroker/history] backitup.0.history.html 2020-11-18 02:00:25.284 - debug: backitup.0 (4228) [iobroker/history] backitup.0.history.json 2020-11-18 02:00:25.436 - debug: backitup.0 (4228) [iobroker] exec: done 2020-11-18 02:00:25.684 - error: host.iobroker_server Caught by controller[0]: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: 2020-11-18 02:00:25.690 - error: host.iobroker_server Caught by controller[1]: Error: Rate Limit Exceeded 2020-11-18 02:00:25.691 - error: host.iobroker_server Caught by controller[1]: at Gaxios._request (/opt/iobroker/node_modules/gaxios/src/gaxios.ts:112:15) 2020-11-18 02:00:25.691 - error: host.iobroker_server Caught by controller[1]: at process._tickCallback (internal/process/next_tick.js:68:7) 2020-11-18 02:00:25.691 - info: host.iobroker_server instance system.adapter.backitup.0 terminated with code 0 (NO_ERROR) 2020-11-18 02:00:25.692 - info: host.iobroker_server Restart adapter system.adapter.backitup.0 because enabled 2020-11-18 02:00:25.796 - info: coronavirus-statistics.0 (6380) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2020-11-18 02:00:26.321 - info: host.iobroker_server instance system.adapter.coronavirus-statistics.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2020-11-18 02:00:55.715 - info: host.iobroker_server instance system.adapter.backitup.0 started with pid 6421 2020-11-18 02:00:59.737 - debug: backitup.0 (6421) Redis Objects: Use Redis connection: 127.0.0.1:9001 2020-11-18 02:00:59.785 - debug: backitup.0 (6421) Objects client ready ... initialize now 2020-11-18 02:00:59.792 - debug: backitup.0 (6421) Objects create System PubSub Client 2020-11-18 02:00:59.793 - debug: backitup.0 (6421) Objects create User PubSub Client 2020-11-18 02:00:59.794 - debug: backitup.0 (6421) Objects client initialize lua scripts 2020-11-18 02:00:59.814 - debug: backitup.0 (6421) Objects connected to redis: 127.0.0.1:9001 2020-11-18 02:00:59.859 - debug: backitup.0 (6421) objectDB connected 2020-11-18 02:00:59.862 - debug: backitup.0 (6421) Redis States: Use Redis connection: 127.0.0.1:9000 2020-11-18 02:00:59.872 - debug: backitup.0 (6421) States create User PubSub Client 2020-11-18 02:00:59.875 - debug: backitup.0 (6421) States create System PubSub Client 2020-11-18 02:00:59.889 - debug: backitup.0 (6421) States connected to redis: 127.0.0.1:9000 2020-11-18 02:00:59.890 - debug: backitup.0 (6421) statesDB connected 2020-11-18 02:01:01.712 - debug: backitup.0 (6421) Plugin sentry Initialize Plugin (enabled=true) 2020-11-18 02:01:01.958 - info: backitup.0 (6421) starting. Version 1.7.0 in /opt/iobroker/node_modules/iobroker.backitup, node: v10.22.0, js-controller: 3.1.4 2020-11-18 02:01:02.076 - info: backitup.0 (6421) [iobroker] backup was activated at 02:00 every 1 day(s) 2020-11-18 02:01:05.499 - debug: backitup.0 (6421) detect backup file 1: iobroker_2020_11_17-09_51_33_backupiobroker.tar.gz 2020-11-18 02:01:05.500 - debug: backitup.0 (6421) detect backup file 2: iobroker_2020_11_17-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.500 - debug: backitup.0 (6421) detect backup file 3: iobroker_2020_11_11-09_37_06_backupiobroker.tar.gz 2020-11-18 02:01:05.501 - debug: backitup.0 (6421) detect backup file 4: iobroker_2020_11_11-09_23_21_backupiobroker.tar.gz 2020-11-18 02:01:05.501 - debug: backitup.0 (6421) detect backup file 5: iobroker_2020_11_03-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.502 - debug: backitup.0 (6421) detect backup file 6: iobroker_2020_10_31-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.502 - debug: backitup.0 (6421) detect backup file 7: iobroker_2020_10_23-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.503 - debug: backitup.0 (6421) detect backup file 8: iobroker_2020_10_20-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.503 - debug: backitup.0 (6421) detect backup file 9: iobroker_2020_10_18-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.503 - debug: backitup.0 (6421) detect backup file 10: iobroker_2020_10_16-02_00_20_backupiobroker.tar.gz 2020-11-18 02:01:05.504 - debug: backitup.0 (6421) detect backup file 11: iobroker_2020_10_14-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.504 - debug: backitup.0 (6421) detect backup file 12: iobroker_2020_10_13-13_21_49_backupiobroker.tar.gz 2020-11-18 02:01:05.505 - debug: backitup.0 (6421) detect backup file 13: iobroker_2020_10_13-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.505 - debug: backitup.0 (6421) detect backup file 14: iobroker_2020_10_12-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.505 - debug: backitup.0 (6421) detect backup file 15: iobroker_2020_10_11-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.506 - debug: backitup.0 (6421) detect backup file 16: iobroker_2020_10_10-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.506 - debug: backitup.0 (6421) detect backup file 17: iobroker_2020_10_09-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.507 - debug: backitup.0 (6421) detect backup file 18: iobroker_2020_10_08-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.507 - debug: backitup.0 (6421) detect backup file 19: iobroker_2020_10_07-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.508 - debug: backitup.0 (6421) detect backup file 20: iobroker_2020_10_06-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.508 - debug: backitup.0 (6421) detect backup file 21: iobroker_2020_10_05-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.508 - debug: backitup.0 (6421) detect backup file 22: iobroker_2020_10_04-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.509 - debug: backitup.0 (6421) detect backup file 23: iobroker_2020_10_03-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.509 - debug: backitup.0 (6421) detect backup file 24: iobroker_2020_10_02-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.510 - debug: backitup.0 (6421) detect backup file 25: iobroker_2020_10_01-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.510 - debug: backitup.0 (6421) detect backup file 26: iobroker_2020_09_30-07_40_09_backupiobroker.tar.gz 2020-11-18 02:01:05.510 - debug: backitup.0 (6421) detect backup file 27: iobroker_2020_09_30-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.511 - debug: backitup.0 (6421) detect backup file 28: iobroker_2020_09_29-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.511 - debug: backitup.0 (6421) detect backup file 29: iobroker_2020_09_28-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.512 - debug: backitup.0 (6421) detect backup file 30: iobroker_2020_09_27-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.512 - debug: backitup.0 (6421) detect backup file 31: iobroker_2020_09_26-02_00_10_backupiobroker.tar.gz 2020-11-18 02:01:05.512 - debug: backitup.0 (6421) detect backup file 32: iobroker_2020_09_25-14_11_27_backupiobroker.tar.gz 2020-11-18 02:01:05.516 - debug: backitup.0 (6421) detect last backup file: iobroker_2020_11_17-09_51_33_backupiobroker.tar.gz
Ich wäre über Hilfe dankbar.
LG Phil82 -
@Phil82
Es gibt mit der Cloud von Google leider Probleme, wo wir bereits ein Issue offen haben.
Wieviel Backups speicherst du in Drive? So wie ich das verstehe, sind es wohl zu viele Anfragen, was auf eine hohe Anzahl an Backups liegen könnte.