Hi
Command line access is disabled by default... I assume this is by design.
It did caught me out a bit. I was wondering if it would not be better to
allow access by default... to keep things simple?
In the mean time I have updated
https://fedorahosted.org/cobbler/wiki/UsingCobblerImport
To
On Thu, Nov 10, 2011 at 3:10 AM, Gerhardus Geldenhuis
gerhardus.geldenh...@gmail.com wrote:
Hi
Command line access is disabled by default... I assume this is by design. It
did caught me out a bit. I was wondering if it would not be better to allow
access by default... to keep things simple?
H,
I thought I tested it
Doing a re-install again it now works where as previously I could not login
if I did not change the file called /etc/cobbler/auth.conf
Maybe something else was wrong.
I am using vanilla 5.6 Red Hat and
cobbler-web-2.2.1-1.el5
cobbler-2.2.1-1.el5
Any ideas why
I have set up a cobbler server to kickstart/build HP ProLiant boxen of various
flavors with RHEL5
I have a particularly stubborn DL380 G5 that refuses to be
PXE-booted/net-installed
I suspect a FUBAR from the guy that manages the DNS/DHCP, but I need more
evidence.
When it tries to PXE-boot,
On 11/10/2011 09:47 AM, Dan White wrote:
I have set up a cobbler server to kickstart/build HP ProLiant boxen of
various flavors with RHEL5
I have a particularly stubborn DL380 G5 that refuses to be
PXE-booted/net-installed
I suspect a FUBAR from the guy that manages the DNS/DHCP, but I
I too have run into this issue. Just like Orion, the solution for me was
'spanning-tree portfast' on the switch port itself on our Cisco switches. The
issue seems to be compounded by the fact that kickstart installs seem to insist
on requesting a DHCP address 3 times during the install
Hey Sr,
I have had this problem a simple kickstart system before, and t was related to
reverse DNS resolution, in my case as it was a simple environment I just used
the option dns=nodns
From: bpe...@secureworks.com
To: cobbler@lists.fedorahosted.org
Subject: RE: Weird Kickstart Problem In
Hi Dan,
I have seen timeout issues like this caused by the switch connected to the
server not bringing the port up in time for the PXE request to be answered.
In that case I had to enable 'spanning-tree portfast' (in Cisco speak) on
the port I was connected to, or disable spanning-tree.
HTH
Where do I add this option ?
On Nov 10, 2011, at 4:09 PM, antonio teixeira gomes jr wrote:
Hey Sr,
I have had this problem a simple kickstart system before, and t was related
to reverse DNS resolution, in my case as it was a simple environment I just
used the option dns=nodns
From:
On Nov 10, 2011, at 1:11 PM, Orion Poplawski wrote:
On 11/10/2011 09:47 AM, Dan White wrote:
I have set up a cobbler server to kickstart/build HP ProLiant boxen of
various flavors with RHEL5
I have a particularly stubborn DL380 G5 that refuses to be
PXE-booted/net-installed
I suspect
Dan White y...@comcast.net wrote:
On Nov 10, 2011, at 1:11 PM, Orion Poplawski wrote:
On 11/10/2011 09:47 AM, Dan White wrote:
I have set up a cobbler server to kickstart/build HP ProLiant boxen of
various flavors with RHEL5
I have a particularly stubborn DL380 G5 that refuses to be
I have set up a cobbler server to kickstart/build HP ProLiant boxen of various
flavors with RHEL5
I have a particularly stubborn DL380 G5 that refuses to be
PXE-booted/net-installed
I suspect a FUBAR from the guy that manages the DNS/DHCP, but I need more
evidence.
When it tries to PXE-boot,
12 matches
Mail list logo
