search

tteck / Proxmox

Proxmox VE Helper-Scripts
https://Helper-Scripts.com
MIT License
14.42k stars 2.37k forks source link

ERROR 2@134 Unknown failure occurred while installing photoprism #631

Closed besynnerlig closed 2 years ago

besynnerlig commented 2 years ago

Describe the issue While installing photoprism on Proxmox Virtual Environment 7.2-7, the following unexpected error happens: Building PhotoPrism (Patience)...‼ ERROR 2@134 Unknown failure occurred.

I have tried default settings and advanced settings with the same result.

Screenshots image

tteck commented 2 years ago

No issues here. Try increasing the "Allocated Cores" and/or "Allocated RAM" to build PhotoPrism.

    ____  __  ______  __________  ____  ____  _________ __  ___
   / __ \/ / / / __ \/_  __/ __ \/ __ \/ __ \/  _/ ___//  |/  /
  / /_/ / /_/ / / / / / / / / / / /_/ / /_/ // / \__ \/ /|_/ / 
 / ____/ __  / /_/ / / / / /_/ / ____/ _, _// / v4_/ / /  / /  
/_/   /_/ /_/\____/ /_/  \____/_/   /_/ |_/___//____/_/  /_/   

Using Advanced Settings
Using Container Type: 1
Using Root Password: Automatic Login
Using Container ID: 111
Using Hostname: photoprism
Using Disk Size: 8
Allocated Cores: 2
Allocated RAM: 2048
Using Bridge: vmbr0
Using IP Address: 192.168.86.252/24
Using Gateway IP Address: 192.168.86.1
Using MAC Address: Default
Using Vlan: Default
Creating a PhotoPrism LXC using the above advanced settings
 ✓ Using local for Template Storage.
 ✓ Using local-lvm for Container Storage.
 ✓ Updated LXC Template List
 ✓ LXC Container 111 was successfully created.
 ✓ Started LXC Container
 ✓ Set up Container OS
 ✓ Network Connected: 192.168.86.252 
 ✓ Internet Connected
 ✓ DNS Resolved github.com to 140.82.114.3
 ✓ Updated Container OS
 ✓ Installed Dependencies
 ✓ Set up Node.js Repository
 ✓ Installed Node.js
 ✓ Installed Golang
 ✓ Installed Tensorflow
 ✓ Cloned PhotoPrism
 ✓ Built PhotoPrism
 ✓ Created Service
 ✓ Customized Container
 ✓ Cleaned
 ✓ Completed Successfully!

PhotoPrism should be reachable by going to the following URL.
         http://192.168.86.252:2342
tteck commented 2 years ago

https://github.com/tteck/Proxmox/issues/449

besynnerlig commented 2 years ago 
   / __ \/ / / / __ \/_  __/ __ \/ __ \/ __ \/  _/ ___//  |/  /
  / /_/ / /_/ / / / / / / / / / / /_/ / /_/ // / \__ \/ /|_/ / 
 / ____/ __  / /_/ / / / / /_/ / ____/ _, _// / v4_/ / /  / /  
/_/   /_/ /_/\____/ /_/  \____/_/   /_/ |_/___//____/_/  /_/   

Using Advanced Settings
Using Container Type: 1
Using Root Password: Automatic Login
Using Container ID: 113
Using Hostname: photoprism
Using Disk Size: 32
Allocated Cores: 4
Allocated RAM: 4096
Using Bridge: vmbr0
Using IP Address: dhcp
Using Gateway IP Address: Default
Using MAC Address: DA:F8:CE:01:16:5C
Using Vlan: Default
Creating a PhotoPrism LXC using the above advanced settings
 ✓ Using local for Template Storage.
 ✓ Using Local-NVMe for Container Storage.
 ✓ Updated LXC Template List
 ✓ LXC Container 113 was successfully created.
 ✓ Started LXC Container
 ✓ Set up Container OS
 ✓ Network Connected: 192.168.4.32 
 ✓ Internet Connected
 ✓ DNS Resolved github.com to 140.82.121.4
 ✓ Updated Container OS
 ✓ Installed Dependencies
 ✓ Set up Node.js Repository
 ✓ Installed Node.js
 ✓ Installed Golang
 ✓ Installed Tensorflow
 ✓ Cloned PhotoPrism
 - Building PhotoPrism (Patience)...‼ ERROR 2@134 Unknown failure occurred.

Unfortunately the problem persists. Is there anything else that I can try?

tteck commented 2 years ago

More power Scotty! Seriously, try more cores. These are vCPU's so depending on your machine it may just take more. Have you watched to see how bad it's beating on the CPU?

besynnerlig commented 2 years ago

She can'nae take any more, captain!

    ____  __  ______  __________  ____  ____  _________ __  ___
   / __ \/ / / / __ \/_  __/ __ \/ __ \/ __ \/  _/ ___//  |/  /
  / /_/ / /_/ / / / / / / / / / / /_/ / /_/ // / \__ \/ /|_/ / 
 / ____/ __  / /_/ / / / / /_/ / ____/ _, _// / v4_/ / /  / /  
/_/   /_/ /_/\____/ /_/  \____/_/   /_/ |_/___//____/_/  /_/   

Using Advanced Settings
Using Container Type: 1
Using Root Password: Automatic Login
Using Container ID: 113
Using Hostname: photoprism
Using Disk Size: 32
Allocated Cores: 8
Allocated RAM: 8192
Using Bridge: vmbr0
Using IP Address: dhcp
Using Gateway IP Address: Default
Using MAC Address: DA:F8:CE:01:16:5C
Using Vlan: Default
Creating a PhotoPrism LXC using the above advanced settings
 ✓ Using local for Template Storage.
 ✓ Using Local-NVMe for Container Storage.
 ✓ Updated LXC Template List
 ✓ LXC Container 113 was successfully created.
 ✓ Started LXC Container
 ✓ Set up Container OS
 ✓ Network Connected: 192.168.4.32 
 ✓ Internet Connected
 ✓ DNS Resolved github.com to 140.82.121.3
 ✓ Updated Container OS
 ✓ Installed Dependencies
 ✓ Set up Node.js Repository
 ✓ Installed Node.js
 ✓ Installed Golang
 ✓ Installed Tensorflow
 ✓ Cloned PhotoPrism
 - Building PhotoPrism (Patience)...‼ ERROR 2@134 Unknown failure occurred.
besynnerlig commented 2 years ago

image

tteck commented 2 years ago

LOL, Dang! It should've built with that! I've encountered issues with cache being a problem before. Try clearing browser cache and try again.

besynnerlig commented 2 years ago

LOL, Dang! It should've built with that! I've encountered issues with cache being a problem before. Try clearing browser cache and try again.

I tried that. Same result unfortunately.

tteck commented 2 years ago

I have no other things to try, 🤷🏻‍♂️ I've never had a build to fail using the amount of resources that you're using.

besynnerlig commented 2 years ago

Thanks anyway for your efforts which I appreciate. Let me know if you come to think of something :)

tteck commented 2 years ago

Last hope 🤞🏻 Try

I increased the node ram amount from 2gb to 4 gb https://github.com/tteck/Proxmox/blob/fe0359f701d1869a2a75d12be0d1e6f7054bd174/setup/photoprism-install.sh#L134

tteck commented 2 years ago

That also gives a different script location to defeat any cache

besynnerlig commented 2 years ago

Thanks. It still fails while building...

    ____  __  ______  __________  ____  ____  _________ __  ___
   / __ \/ / / / __ \/_  __/ __ \/ __ \/ __ \/  _/ ___//  |/  /
  / /_/ / /_/ / / / / / / / / / / /_/ / /_/ // / \__ \/ /|_/ / 
 / ____/ __  / /_/ / / / / /_/ / ____/ _, _// / v4_/ / /  / /  
/_/   /_/ /_/\____/ /_/  \____/_/   /_/ |_/___//____/_/  /_/   

Using Advanced Settings
Using Container Type: 1
Using Root Password: Automatic Login
Using Container ID: 113
Using Hostname: photoprism
Using Disk Size: 32
Allocated Cores: 8
Allocated RAM: 8192
Using Bridge: vmbr0
Using IP Address: dhcp
Using Gateway IP Address: Default
Using MAC Address: DA:F8:CE:01:16:5C
Using Vlan: Default
Creating a PhotoPrism LXC using the above advanced settings
 ✓ Using local for Template Storage.
 ✓ Using Local-NVMe for Container Storage.
 ✓ Updated LXC Template List
 ✓ LXC Container 113 was successfully created.
 ✓ Started LXC Container
 ✓ Set up Container OS
 ✓ Network Connected: 192.168.4.32 
 ✓ Internet Connected
 ✓ DNS Resolved github.com to 140.82.121.4
 ✓ Updated Container OS
 ✓ Installed Dependencies
 ✓ Set up Node.js Repository
 ✓ Installed Node.js
 ✓ Installed Golang
 ✓ Installed Tensorflow
 ✓ Cloned PhotoPrism
 - Building PhotoPrism (Patience)...‼ ERROR 2@134 Unknown failure occurred.
tteck commented 2 years ago

WOW, I have no idea why

besynnerlig commented 2 years ago

As strange as it seems, the problem is that my Hurricane Electric IPv6 tunnel on my router needs to be up and operatable. My communications operator Telia Öppen Fiber hasn't bothered to enable native IPv6 so I'm stuck in the 1980's with IPv4 and NAT. My Hurricane Electric IPv6 tunnel can provide IPv6 connectivity but it's quite slow so I had turned it off to force IPv4 which is way faster. However my LAN clients are still configured with a valid IPv6 address through SLAAC. Well, that's the background. Just by starting the IPv6 tunnel again, the install script runs great! However without investigating any further i get a ERR_CONNECTION_REFUSED error when opening the URL provided at the final stage by the install script. That is a completely different issue which I will try to solve soon. EDIT: (Solved https://github.com/tteck/Proxmox/issues/635#issuecomment-1277791462)

Thanks again for your kind help @tteck