Bash <(wget -qO- getamp.sh) as root and it just sits there no errors no CPU usage

Technical Support
1

Note - If you do not fill in every section below, your post won’t be answered - you must provide the steps you have followed so far and the actions you’ve already taken. Make sure to remove this notice from your post too.

Screenshots of text are prohibited. Always copy and paste text as text.

Make sure you search before posting! Duplicate posts for the same issue may not be answered.

OS Name/Version:Ubuntu 24.04 inside of proxmox running as a VM

Product Name/Version: AMP ‘Phobos’ 2.6.0

Problem Description: using the install script just does nothing it seems.

If you're sharing console output, logs, or commands you have run, please make sure to use code tags 
(3x backticks for blocks, 1x backtick for a single line) to help make posts readable. This also
provides syntax highlighting.

Steps to reproduce:

  • Step 1 sudo su
  • Step 2 bash script
  • Step 3 stare at the screen and question your life decisions.

Actions taken to resolve so far: so far i have ran this on one VM I have been working on networks and web servers and DNS for hours so I am probably missing something really dumb and this question is going to embarrass me.

I have tried from different directories as root the last command has been sitting and doing nothing for the past 30 minutes and its just blank. no CLI to tell me whats going on.

2

Like nothing as in no output whatsoever? Or just stops outputting at a certain point?

3

nope just tried on a different VM and it runs just fine but fails because port forwarding isn’t setup for it.

on the VM it doesn’t work on it got 4 cores 4 gigs of ram and 128 gigs of storage.

the VM it works on has 2 cores 2 gigs of ram and 32 gigs of storage.

I say works but I mean the script at least runs. The VM that does nothing with the script already has a working nginx config on it and nothing else.

4

Weird, I wonder if it’ll work if you run bash <(wget -qO- getamp.sh) addRepo first and then the full install script. It could be getting hung up on something funky

5

Run simply wget getamp.sh and see what you get. Could be an IPv6 or DNS issue

6

So just to close this it had nothing to do with AMP. AT ALL. It was a bad install somehow the install got corrupted and wouldn’t run anything with wget. I am not sure how that even happens but it was a fresh VM so I just deleted it and built a new one. No issues this time.