AGAIN, proxmox backup server doesn't accept connection after install & reboot

[luca_merkle]

Followed my own procedure used on a local VM to understand why PBS doesn't accept incoming connection anymore after first installation, but it failed on my host in cloud.

Again, can't connect anymore to my PBS box.

The problem is clearly in PBS setup as the VM is perfectly working and rebooting until it's a debian-only without an installed PBS (no subscriptions), and I think maintainer should fix this.

Maybe there's a conflict between ifupdown and ifupdown2 as they are concurrently installed.
As a matter of fact, when installing PBS, I noticed an ifupdown upgrade, but as ifupdown 1 & 2 can't co-exist, PBS should make its choice and get rid of one of the two.

Thanks,
Luca

 

[oversite]

Followed my own procedure used on a local VM to understand why PBS doesn't accept incoming connection anymore after first installation, but it failed on my host in cloud.

Again, can't connect anymore to my PBS box.

The problem is clearly in PBS setup as the VM is perfectly working and rebooting until it's a debian-only without an installed PBS (no subscriptions), and I think maintainer should fix this.

Maybe there's a conflict between ifupdown and ifupdown2 as they are concurrently installed.
As a matter of fact, when installing PBS, I noticed an ifupdown upgrade, but as ifupdown 1 & 2 can't co-exist, PBS should make its choice and get rid of one of the two.

Thanks,
Luca

Sorry Luca but i don't understand what you are asking. Did you install PBS in a VM running debian? And after that you cannot start the VM?

.. do you have many threads about this???
https://forum.proxmox.com/threads/p...accept-connection-after-install-reboot.79441/

 

[luca_merkle]

Sorry Luca but i don't understand what you are asking. Did you install PBS in a VM running debian? And after that you cannot start the VM?

.. do you have many threads about this???
https://forum.proxmox.com/threads/p...accept-connection-after-install-reboot.79441/

The VM doesn't accept incoming connections after a fresh install of PBS 1.0.1 on Debian 10.
It works perfectly until I do not install PBS.

I do not know what PBS is exactly doing and installing, but it happens that I have a VM without networking.
When installing PBS 1.0.1, I see:
"installing new config into /etc/default/networking" in the console output as the only thing related to networking, but I really don't know what is changing and happening.

Problem is, when I install PBS, networking doesn't work anymore.

Thanks,
Luca

 

[luca_merkle]

Sorry Luca but i don't understand what you are asking. Did you install PBS in a VM running debian? And after that you cannot start the VM?

.. do you have many threads about this???
https://forum.proxmox.com/threads/p...accept-connection-after-install-reboot.79441/

I also noticed that PBS install is removing some directories.


root@rs003928:/etc/network# ls -l
total 28
drwxr-xr-x 2 root root 4096 Nov 22 18:19 if-down.d
drwxr-xr-x 2 root root 4096 Nov 22 18:19 if-up.d
drwxr-xr-x 3 root root 4096 Nov 22 18:19 ifupdown2
-rw-r--r-- 1 root root 713 Nov 22 18:13 interfaces
drwxr-xr-x 2 root root 4096 Sep 25 09:17 interfaces.d

it removed if-pre-up.d

may be this is one of the problem.

 

[oversite]

I also noticed that PBS install is removing some directories.


root@rs003928:/etc/network# ls -l
total 28
drwxr-xr-x 2 root root 4096 Nov 22 18:19 if-down.d
drwxr-xr-x 2 root root 4096 Nov 22 18:19 if-up.d
drwxr-xr-x 3 root root 4096 Nov 22 18:19 ifupdown2
-rw-r--r-- 1 root root 713 Nov 22 18:13 interfaces
drwxr-xr-x 2 root root 4096 Sep 25 09:17 interfaces.d

it removed if-pre-up.d

may be this is one of the problem.

It would help to know how you installed pbs, apt-get install proxmox-backup-server or apt-get install proxmox-backup?

 

[luca_merkle]

It would help to know how you installed pbs, apt-get install proxmox-backup-server or apt-get install proxmox-backup?

I followed the guide at https://pbs.proxmox.com/docs/installation.html#proxmox-backup-no-subscription-repository
and I did a
apt-get install proxmox-backup-server

 

[oversite]

I followed the guide at https://pbs.proxmox.com/docs/installation.html#proxmox-backup-no-subscription-repository
and I did a
apt-get install proxmox-backup-server

thanks. A netstat output could help, like netstat -tunlp also how the /etc/network/interfaces looks like. If you don't have netstat can be installed with apt install net-tools

 

[luca_merkle]

I attach 2 screenshots as I can't ssh into the box, so a I do VNC.
It doesn't accept any incoming connection (outgoing are working)
Those are after a fresh install and a reboot, it happens every time I do an install.

 

[oversite]

And it's a VM not a CT right? And you could ssh to it before installing pbs? to root?
No other changes except vanilla debian 10?
I have installed one working pbs on debian 10 on VM. I right now installed one on CT using the provided debian 10 template, using static ipv4 ip no dhcp, assigning the IP in proxmox GUI, following the same guide you said, both are working fine. apt install proxmox-backup-server for sure does install plenty, LVM2, ifupdown2 etc but it works fine so i cannot reproduce.
Sorry cannot be of any more help but suggest test a plain install on CT debian 10 (it's so easy anyway) with static local IP, it really should work.

 

[luca_merkle]

I managed to find out something:
I did many reboots and still no way to connect to this box.
Then I did a
systemctl restart networking
and everything was fixed, even after a reboot.

But I really do not understand what's happening.
I also noticed I am not the only one in this forum to have such an issue.

Thanks for your help.

And it's a VM not a CT right? And you could ssh to it before installing pbs? to root?
No other changes except vanilla debian 10?
I have installed one working pbs on debian 10 on VM. I right now installed one on CT using the provided debian 10 template, using static ipv4 ip no dhcp, assigning the IP in proxmox GUI, following the same guide you said, both are working fine. apt install proxmox-backup-server for sure does install plenty, LVM2, ifupdown2 etc but it works fine so i cannot reproduce.
Sorry cannot be of any more help but suggest test a plain install on CT debian 10 (it's so easy anyway) with static local IP, it really should work.

It's a dedicated server on Myloc.
it's really driving me crazy.
I do setup test here locally on vmware starting from vanilla debian 10 and everything is fine, I do it on Myloc and something goes crazy.

Thank you anyway!

 

[fortechitsolutions]

Hi, I wanted to post on this thread because it seems directly relevant. I've setup ~3 x PBS servers in the last 2 months and I think I am seeing the same problem. General trend:

- one case it was a dedicated physical host, debian10 minimal install on SW Raid / local mirror of 2 x 6tb drives. Debian is installed and working fine.
- then I start install of PBS as per wiki, Installation — Proxmox Backup 1.0.1-1 documentation - key step is to add the APT repo source. Then issue command, "apt-get install proxmox-backup". It happily chugs along, then gets to step shown below, and hangs. Loses network. Getting console / reboot the box / and networ is still dead. In one case a reboot, then reinstall from console - not over remote SSH session - seemed sufficient.

It hangs here:

root@debian:~# apt-get install proxmox-backup-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  irqbalance libnuma1 linux-image-4.9.0-12-amd64 runit-helper
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  fonts-font-awesome ifupdown2 libfuse3-3 libjs-extjs libnvpair1linux libuutil1linux libzfs2linux libzpool2linux mt-st mtx pbs-i18n
  proxmox-backup-docs proxmox-mini-journalreader proxmox-widget-toolkit pve-xtermjs smartmontools zfs-zed zfsutils-linux
Suggested packages:
  bridge-utils ethtool python3-gvgen python3-mako fuse3 gsmartcontrol smart-notifier nfs-kernel-server samba-common-bin zfs-initramfs
The following packages will be REMOVED:
  ifupdown
The following NEW packages will be installed:
  fonts-font-awesome ifupdown2 libfuse3-3 libjs-extjs libnvpair1linux libuutil1linux libzfs2linux libzpool2linux mt-st mtx pbs-i18n
  proxmox-backup-docs proxmox-backup-server proxmox-mini-journalreader proxmox-widget-toolkit pve-xtermjs smartmontools zfs-zed zfsutils-linux
0 upgraded, 19 newly installed, 1 to remove and 4 not upgraded.
Need to get 16.9 MB of archives.
After this operation, 77.2 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 ifupdown2 all 3.0.0-1+pve3 [227 kB]
Get:2 http://ftp.ca.debian.org/debian buster/main amd64 fonts-font-awesome all 5.0.10+really4.7.0~dfsg-1 [515 kB]
Get:3 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 libjs-extjs all 6.0.1-10 [2,505 kB]
Get:4 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 libnvpair1linux amd64 0.8.5-pve1 [52.2 kB]
Get:5 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 libuutil1linux amd64 0.8.5-pve1 [45.2 kB]
Get:6 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 libzfs2linux amd64 0.8.5-pve1 [217 kB]
Get:7 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 libzpool2linux amd64 0.8.5-pve1 [816 kB]
Get:8 http://ftp.ca.debian.org/debian buster/main amd64 libfuse3-3 amd64 3.4.1-1+deb10u1 [81.2 kB]
Get:9 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 pbs-i18n all 2.2-2 [48.7 kB]
Get:10 http://ftp.ca.debian.org/debian buster/main amd64 mt-st amd64 1.3-2 [36.2 kB]
Get:11 http://ftp.ca.debian.org/debian buster/main amd64 mtx amd64 1.3.12-12 [104 kB]
Get:12 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 proxmox-backup-docs all 1.0.6-1 [2,165 kB]
Get:13 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 proxmox-mini-journalreader amd64 1.1-1 [6,280 B]
Get:14 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 proxmox-widget-toolkit all 2.4-3 [64.8 kB]
Get:15 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 pve-xtermjs amd64 4.7.0-3 [585 kB]
Get:16 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 smartmontools amd64 7.1-pve2 [539 kB]
Get:17 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 proxmox-backup-server amd64 1.0.6-1 [8,482 kB]
Get:18 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 zfsutils-linux amd64 0.8.5-pve1 [368 kB]
Get:19 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 zfs-zed amd64 0.8.5-pve1 [65.6 kB]
Fetched 16.9 MB in 2s (6,891 kB/s)
(Reading database ... 52085 files and directories currently installed.)
Removing ifupdown (0.8.35) ...

(STOPS HERE)

So it seems once it removes ifupdown - things go to hell.


In another case - Clean install VM / Debian10 / updated to latest. Follow same steps detailed above. Hangs at same point, with me doing setup via a SSH session. Note the VM is different place from proxmox it will be linked to. It is also a place I've managed to get a few PBS installs done without trouble.


I have tried just now, as per earlier hint in this thread,
- get onto console
- login as root
- issue command "systemctl restart networking" - and this did not appear to help in my case.

So.

I am not sure if proxmox team might be willing to try a simple test, ie,

- prep a disoosable test host, a VM or physical box
- clean install Debian 10, minimal, update to latest
- then install PBS and see what happens. And I am guessing you might see this behaviour that is being reported in this thread.

Possibly this falls into the category of "Dude, use the appliance installer, don't bug us with this".
But maybe if you do confirm a problem, at least we can update the PBS Wiki Install doc with a "warning" to specifically say, "hey, some users report this problem when you do a manual install on a base/bare/clean Deb10 Host".


TIm

 

[oversite]

Hi, I wanted to post on this thread because it seems directly relevant. I've setup ~3 x PBS servers in the last 2 months and I think I am seeing the same problem. General trend:

- one case it was a dedicated physical host, debian10 minimal install on SW Raid / local mirror of 2 x 6tb drives. Debian is installed and working fine.
- then I start install of PBS as per wiki, Installation — Proxmox Backup 1.0.1-1 documentation - key step is to add the APT repo source. Then issue command, "apt-get install proxmox-backup". It happily chugs along, then gets to step shown below, and hangs. Loses network. Getting console / reboot the box / and networ is still dead. In one case a reboot, then reinstall from console - not over remote SSH session - seemed sufficient.

It hangs here:

root@debian:~# apt-get install proxmox-backup-server
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages were automatically installed and are no longer required:
  irqbalance libnuma1 linux-image-4.9.0-12-amd64 runit-helper
Use 'apt autoremove' to remove them.
The following additional packages will be installed:
  fonts-font-awesome ifupdown2 libfuse3-3 libjs-extjs libnvpair1linux libuutil1linux libzfs2linux libzpool2linux mt-st mtx pbs-i18n
  proxmox-backup-docs proxmox-mini-journalreader proxmox-widget-toolkit pve-xtermjs smartmontools zfs-zed zfsutils-linux
Suggested packages:
  bridge-utils ethtool python3-gvgen python3-mako fuse3 gsmartcontrol smart-notifier nfs-kernel-server samba-common-bin zfs-initramfs
The following packages will be REMOVED:
  ifupdown
The following NEW packages will be installed:
  fonts-font-awesome ifupdown2 libfuse3-3 libjs-extjs libnvpair1linux libuutil1linux libzfs2linux libzpool2linux mt-st mtx pbs-i18n
  proxmox-backup-docs proxmox-backup-server proxmox-mini-journalreader proxmox-widget-toolkit pve-xtermjs smartmontools zfs-zed zfsutils-linux
0 upgraded, 19 newly installed, 1 to remove and 4 not upgraded.
Need to get 16.9 MB of archives.
After this operation, 77.2 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 ifupdown2 all 3.0.0-1+pve3 [227 kB]
Get:2 http://ftp.ca.debian.org/debian buster/main amd64 fonts-font-awesome all 5.0.10+really4.7.0~dfsg-1 [515 kB]
Get:3 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 libjs-extjs all 6.0.1-10 [2,505 kB]
Get:4 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 libnvpair1linux amd64 0.8.5-pve1 [52.2 kB]
Get:5 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 libuutil1linux amd64 0.8.5-pve1 [45.2 kB]
Get:6 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 libzfs2linux amd64 0.8.5-pve1 [217 kB]
Get:7 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 libzpool2linux amd64 0.8.5-pve1 [816 kB]
Get:8 http://ftp.ca.debian.org/debian buster/main amd64 libfuse3-3 amd64 3.4.1-1+deb10u1 [81.2 kB]
Get:9 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 pbs-i18n all 2.2-2 [48.7 kB]
Get:10 http://ftp.ca.debian.org/debian buster/main amd64 mt-st amd64 1.3-2 [36.2 kB]
Get:11 http://ftp.ca.debian.org/debian buster/main amd64 mtx amd64 1.3.12-12 [104 kB]
Get:12 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 proxmox-backup-docs all 1.0.6-1 [2,165 kB]
Get:13 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 proxmox-mini-journalreader amd64 1.1-1 [6,280 B]
Get:14 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 proxmox-widget-toolkit all 2.4-3 [64.8 kB]
Get:15 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 pve-xtermjs amd64 4.7.0-3 [585 kB]
Get:16 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 smartmontools amd64 7.1-pve2 [539 kB]
Get:17 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 proxmox-backup-server amd64 1.0.6-1 [8,482 kB]
Get:18 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 zfsutils-linux amd64 0.8.5-pve1 [368 kB]
Get:19 http://download.proxmox.com/debian/pbs buster/pbs-no-subscription amd64 zfs-zed amd64 0.8.5-pve1 [65.6 kB]
Fetched 16.9 MB in 2s (6,891 kB/s)
(Reading database ... 52085 files and directories currently installed.)
Removing ifupdown (0.8.35) ...

(STOPS HERE)

So it seems once it removes ifupdown - things go to hell.


In another case - Clean install VM / Debian10 / updated to latest. Follow same steps detailed above. Hangs at same point, with me doing setup via a SSH session. Note the VM is different place from proxmox it will be linked to. It is also a place I've managed to get a few PBS installs done without trouble.


I have tried just now, as per earlier hint in this thread,
- get onto console
- login as root
- issue command "systemctl restart networking" - and this did not appear to help in my case.

So.

I am not sure if proxmox team might be willing to try a simple test, ie,

- prep a disoosable test host, a VM or physical box
- clean install Debian 10, minimal, update to latest
- then install PBS and see what happens. And I am guessing you might see this behaviour that is being reported in this thread.

Possibly this falls into the category of "Dude, use the appliance installer, don't bug us with this".
But maybe if you do confirm a problem, at least we can update the PBS Wiki Install doc with a "warning" to specifically say, "hey, some users report this problem when you do a manual install on a base/bare/clean Deb10 Host".


TIm

just a short question to narrow down the issue, did you use dhcp client or static ipv4 when it breaks?

 

[fortechitsolutions]

Hi, the VM has static assigned IP in most recent case. I think the physical box I was setting up a few weeks ago was DHCP.

 

[fortechitsolutions]

Footnote, I banged my head against this for a while this morning, reinstalled my VM and started over a few times. First pass I noted my debian sources file lacked the 'contrib' stanza on each line; so I added that. (which is recommended in the PBS install hints). Did not change anything. I also note, I can get a more detailed error message. And maybe useful for sequence reference this time.

- Did PBS install packages via VNC remote console (not depending on ssh / network being alive for the VM where I install PBS)
- after install host was still alive / network alive
- reboot and network was dead.
- now in the console if I issue commands as follows, I get a nice clear error:

ifdown eth0

ifup eth0

error: netlink eth0 cannot find address X.Y.Z.ZZ/24 dev eth0: 'srt' object has no attribute 'packed'

Alas google searches tell me - closest I can find is something about ifupdown2 not having env variable set (?) or something like that
but the workaround for that appears to be no change.

anyhow.

not sure if this error helps shed any light.

Thanks,

Tim

 

[fortechitsolutions]

Footnote on this thread, I poked at it again today and appear to have found a bit of a workaround, it feels like a kludge but anyhow, alive and working is better than not-alive-and-not-working, at least for now.

basic endgame.

start with clean deb10 VM provided from hosting provider
get vnc console so I can do steps that won't stop once network drops, ie, do not do install via SSH session

follow initial steps for vanilla install proxmox backup server on top of debian, ie,

  370  wget http://download.proxmox.com/debian/proxmox-ve-release-6.x.gpg -O /etc/apt/trusted.gpg.d/proxmox-ve-release-6.x.gpg
  371  vi /etc/apt/sources.list
 
  make sure all lines end with main contrib instead of just main. For some reason
  stock install here for this vm was only 'main' and lacked 'contrib' stanza
  then
 
  372  apt update
  373  apt-get install proxmox-backup-server

Once this is done. Install proceeds, and as soon as you see the line go by during install re: install of ifupdown2
then network is dead

next step is as per hints from this other thread, kind of:
proxmox backup server doesn't accept connection after install & reboot | Proxmox Support Forum

go into sources dir and edit / comment out the enterprise pbs repo since I don't have a key here.

  377  cd /etc/apt/sources.list.d/
  378  ls -la
  379  more pbs-enterprise.list
  380 vi pbs-enterprise.list   
and add a "#" to front of the line for that entry

once that is done, manually remove ifupdown2 and manually install ifupdown from local cache, as per (approx):

  380  apt remove ifupdown2
  381  apt install ifupdown        # (NOTE (cannot do this / does not work / no network)
  382  which ifupdown               # just checking, yup, nowhere to be found presently.
  383  cd /var/cache/apt/archives/    # Manual cache dir install work steps begin here.
  384  ls -la
  385  ls -la | grep -i ifup
  386  dpkg -i ifupdown_0.7.53.1_amd64.deb   # Note don't use this version, will not install
  387  dpkg -i ifupdown_0.8.19_amd64.deb      # note this one appears to install
  388  apt-get -f install      # Manual tidy up attempt step one
  389  apt-get -f install ifupdown    # and step two, was not really needed I think
  390  service networking restart    # start network
  391  service networking status     # Bingo?
  392  ping 8.8.8.8                               # Bingo?
  393  service networking status      # status looks good but not yet happy
  394  ip address                               # status looks good but not yet happy
  395  cd /etc/apt/sources.list.d/    # make sure this repo is disabled
  396  vi pbs-enterprise.list
  397  apt-get clean                             # tidy up steps as per other thread.
  398  apt-get autoclean
  399  apt-get --purge autoclean
  400  apt-get --purge autoremove
  401  reboot                                           # reboot and see how we fare?
  402  ip address                                     # looks better this time
  403  service networking status          # and also output from this.
  404  ping google.ca                            # happy days, ping is alive, PBS host is accessible via SSH / web admin for PBS port 8007

SO.

Bit of a kludge. We'll see if things break when PBS gets an update in a month-or-whenever.

But for now it appeared to work on this problem host.

I am still unclear what about ifupdown2 made things break on this host; if it was something 'special' about how this VM was prepped by the provider / something about the IP configuration. It looks like a pretty vanilla static IP address setup when I look at the interfaces config file that is preset, so it is weird. It sorta seems to me like something is odd with ifupdown2 related to the proxmox / PBS repo but I am not certain.

Figured I would post this here in case it helps someone else, or at very least helps me if I bump into this again in future

Tim

 

[tettabeta]

We ran into a similar situation.
Installed several times with the PBS install ISO, and lost connectivity after few days.
Interestingly, after "systemctl restart networking" the server is still unreachable BUT the cluster backup are working and the PBS storage appears on each cluster node.
Hope to get to a point where PBS is reliable. Until that date, we will keep our ol'trusted Truenas online.
Brgds
Davide

 

[dcsapak]

t connectivity after few days.
Interestingly, after "systemctl restart networking" the server is still unreachable BUT the cluster backup are working and the PBS storage appears on each cluster node.

but that means the connection works. all backups/operations are done via the https api, so if the pve cluster can access it, but you cannot, there must be another problem in your network/firewall etc.

 

[tettabeta]

but that means the connection works. all backups/operations are done via the https api, so if the pve cluster can access it, but you cannot, there must be another problem in your network/firewall etc.

The point is that we have not configured any FW service on PBS. And PBS segregates itself after hours/days after being working normally.

Tried anything we found on this forum - looks like PBS is still too "beta" at least for customer like us with limited sysadm skills, while PVE is way more mature (we paid three node subscription).

Brgds
Davide

 

[fortechitsolutions]

Hi, for what it is worth. I have been using PBS with ~5 small client deployments in the last few months. Generally speaking once I get past any 'installer time' hiccough, there is zero problem. I don't 'lose access' and it does not 'misbehave' once it is installed-and-working-smoothly. I believe the problem /excitement with my install is in part because I am doing a custom install (ie, install stock debian minimal first with SW Raid, then add PBS on top / afterwards). And some unwanted interaction with ifupdown2 install as part of PBS install that is not actually desirable.

Anyhow all this to say, for clarity

-- PBS for me, once working, appears to work really, really well
-- I do not have 'intermittent or ongoing' network issues. I specifically have problem with a particular phase of the initial PBS install in a specific custom install context
-- once that specific problem is resolved, it is 100% resolved it seems, and I have no fear / complaint / worry. And there are no ongoing/intermittent issues.

ie, if you are having PBS access issues, intermittently after some time, it sounds like a different issue than the one I had described in this thread when I posted to it.

--Tim

 

[oversite]

Hi, for what it is worth. I have been using PBS with ~5 small client deployments in the last few months. Generally speaking once I get past any 'installer time' hiccough, there is zero problem. I don't 'lose access' and it does not 'misbehave' once it is installed-and-working-smoothly. I believe the problem /excitement with my install is in part because I am doing a custom install (ie, install stock debian minimal first with SW Raid, then add PBS on top / afterwards). And some unwanted interaction with ifupdown2 install as part of PBS install that is not actually desirable.

Anyhow all this to say, for clarity

-- PBS for me, once working, appears to work really, really well
-- I do not have 'intermittent or ongoing' network issues. I specifically have problem with a particular phase of the initial PBS install in a specific custom install context
-- once that specific problem is resolved, it is 100% resolved it seems, and I have no fear / complaint / worry. And there are no ongoing/intermittent issues.

ie, if you are having PBS access issues, intermittently after some time, it sounds like a different issue than the one I had described in this thread when I posted to it.

--Tim

This is exactly also how I am experiencing PBS, it is very reliable.
However, I also noticed something strange happening with ifupdown2 when installing, and possibly even more with uninstall and reinstall via apt. The networking really get's screwed up - FUBAR. This does not really bother me but it's not because of someones fw or nw, it's really happening by the installation of PBS thru apt.