Files

defiQUG fe0365757a Update documentation structure and enhance .gitignore

- Added generated index files and report directories to .gitignore to prevent unnecessary tracking of transient files.
- Updated README links to reflect new documentation paths for better navigation.
- Improved documentation organization by ensuring all links point to the correct locations, enhancing user experience and accessibility.

2025-12-12 21:18:55 -08:00

3.9 KiB

Raw Blame History

Copy Script to Proxmox Nodes - Instructions

Script: complete-vm-100-guest-agent-check.sh
Target: Both Proxmox nodes (ml110-01 and r630-01)

Issue

The automated copy script cannot connect to the Proxmox nodes. This may be due to:

Network connectivity issues
Incorrect password in .env file
SSH access restrictions
Firewall rules

Solution: Manual Copy

Option 1: Using SCP (Recommended)

For ml110-01 (Site 1 - 192.168.11.10):

# Load password from .env (adjust if needed)
source .env
PROXMOX_PASS="${PROXMOX_ROOT_PASS:-L@kers2010}"

# Copy script
sshpass -p "$PROXMOX_PASS" scp -o StrictHostKeyChecking=no \
  scripts/complete-vm-100-guest-agent-check.sh \
  root@192.168.11.10:/usr/local/bin/complete-vm-100-guest-agent-check.sh

# Make executable
sshpass -p "$PROXMOX_PASS" ssh -o StrictHostKeyChecking=no root@192.168.11.10 \
  'chmod +x /usr/local/bin/complete-vm-100-guest-agent-check.sh'

# Verify
sshpass -p "$PROXMOX_PASS" ssh -o StrictHostKeyChecking=no root@192.168.11.10 \
  'ls -lh /usr/local/bin/complete-vm-100-guest-agent-check.sh'

For r630-01 (Site 2 - 192.168.11.11):

# Copy script
sshpass -p "$PROXMOX_PASS" scp -o StrictHostKeyChecking=no \
  scripts/complete-vm-100-guest-agent-check.sh \
  root@192.168.11.11:/usr/local/bin/complete-vm-100-guest-agent-check.sh

# Make executable
sshpass -p "$PROXMOX_PASS" ssh -o StrictHostKeyChecking=no root@192.168.11.11 \
  'chmod +x /usr/local/bin/complete-vm-100-guest-agent-check.sh'

# Verify
sshpass -p "$PROXMOX_PASS" ssh -o StrictHostKeyChecking=no root@192.168.11.11 \
  'ls -lh /usr/local/bin/complete-vm-100-guest-agent-check.sh'

Option 2: Copy Script Content Directly

If SCP doesn't work, you can copy the script content directly:

Display the script content:

cat scripts/complete-vm-100-guest-agent-check.sh

SSH to the Proxmox node:

sshpass -p "$PROXMOX_PASS" ssh -o StrictHostKeyChecking=no root@192.168.11.10

On the Proxmox node, create the file:

cat > /usr/local/bin/complete-vm-100-guest-agent-check.sh << 'SCRIPT_EOF'
[paste the entire script content here]
SCRIPT_EOF

chmod +x /usr/local/bin/complete-vm-100-guest-agent-check.sh

Verify:

/usr/local/bin/complete-vm-100-guest-agent-check.sh

Option 3: Use Proxmox Web UI

Access Proxmox Web UI for each node
Go to Shell (or use the console)
Create the file using the web editor or paste the script content

Make it executable:

chmod +x /usr/local/bin/complete-vm-100-guest-agent-check.sh

Verify Script is Installed

After copying, verify on each node:

# On ml110-01
sshpass -p "$PROXMOX_PASS" ssh -o StrictHostKeyChecking=no root@192.168.11.10 \
  '/usr/local/bin/complete-vm-100-guest-agent-check.sh'

# On r630-01
sshpass -p "$PROXMOX_PASS" ssh -o StrictHostKeyChecking=no root@192.168.11.11 \
  '/usr/local/bin/complete-vm-100-guest-agent-check.sh'

Troubleshooting

If "Permission denied" error:

Check password in .env file:
```
grep PROXMOX_ROOT_PASS .env
```
Try connecting manually to verify:
```
ssh root@192.168.11.10
```
Check if password authentication is enabled (may need key-based auth)

If "Connection refused" or "Host unreachable":

Verify network connectivity:
```
ping 192.168.11.10
ping 192.168.11.11
```

Check if SSH is running on Proxmox nodes:

nmap -p 22 192.168.11.10
nmap -p 22 192.168.11.11

Verify firewall rules allow SSH access

Quick Reference

Script Location: scripts/complete-vm-100-guest-agent-check.sh
Target Location: /usr/local/bin/complete-vm-100-guest-agent-check.sh
Nodes:

ml110-01: 192.168.11.10
r630-01: 192.168.11.11

Password: Check .env file for PROXMOX_ROOT_PASS

Last Updated: 2025-12-11

3.9 KiB Raw Blame History