Project

General

Profile

Actions
Copy link

Bug #2992

closed

Boot problem after upgrade

Added by Ernesto Sitoe over 11 years ago. Updated almost 9 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
bandwidthd
Target version:
-
Start date:
05/14/2013
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:

Description

I recently upgraded my pfSense 2.0.2 to 2.0.3 and is no longer working
as expected. It stops in the following line:
Starting package bandwidth...Enter full pathname of shell ot RETURN for /bin/bash:

After i hit RETURN it goes nowhere.

Actions
Copy link
 #1

Updated by Jim Pingle over 11 years ago

  • Project changed from 3 to pfSense Packages
  • Category set to bandwidthd

I've seen a few sporadic reports of this from reliable sources, so I know it's an issue, but I've tried replicating it several different ways and it has yet to happen for me in a test environment or any live system I've had my hands on.

A few things we'll need to know:
  • i386 or amd64?
  • Was bandwidthd already on the latest version before the upgrade?
  • What other packages do you have installed?
  • We need to see the <installedpackages> ... </installedpackages> section of your config.xml file
  • Also need to see the contents of:
    • ls -l /usr/local/pkg/
    • ls -l /usr/local/etc/
Actions
Copy link
 #2

Updated by Jim Pingle over 11 years ago

  • Status changed from New to Feedback

Needs info on how to reproduce it before anything can be done.

Actions
Copy link
 #3

Updated by Eric Green almost 11 years ago

This happened to me today. It happened on a fresh install with only bandwidthd and openvpn installed, after I changed some firewall rules. I got it to work again by renaming the /usr/local/bandwidthd directory to something else and forcing a reboot. So it does not appear to be an upgrade as such that triggers it, but, rather, perhaps related to the upgrade mucking with the firewall rules.

Easiest workaround is, when you're dumped to the prompt, 'mv /usr/local/bandwidthd /usr/local/bandwidthd-' and reboot. Then remove bandwidthd via the application manager once the system comes back up. So clearly it's a bandwidthd issue, but what exactly, is unknown.

Actions
Copy link
 #4

Updated by System IT about 10 years ago

Hello,

New 2.1.4 install here, then upgraded to 2.1.5.

I then installed bandwidthd and just had the no boot issue where it hits

Starting bandwidthd...Enter full pathname of shell or RETURN for /bin/sh:

The renaming of the directory for me did not work (bandwidthdsucks , although it doesn't when it works), i confirmed the folder name change and exited the shell and the same error came up upon trying to boot again.

Looks like i have to whipe this box and start all over.

Actions
Copy link
 #5

Updated by Chris Buechler almost 9 years ago

  • Status changed from Feedback to Duplicate

duplicate of #3986

Actions
Copy link

Also available in: Atom PDF