Thanks for this bug report.
I can confirm that the lvm installation of saucy64 can be fixed by
booting a rescue cd and installing lvm2/libdevmapper-event1.02.1 by
hand.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi Lorello,
In the puppet source code at github you can see how the status is
checked via upstart:
https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/upstart.rb
The is a search for 'start' on the status output. So if ssh is running
and status ssh gives the following
Hi Lorello,
In the puppet source code at github you can see how the status is
checked via upstart:
https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/upstart.rb
The is a search for 'start' on the status output. So if ssh is running
and status ssh gives the following
Public bug reported:
As requested by Micah Gersten:
When purging and installing puppetmaster-passenger again it wont start.
This is somehow due to a2enmod passenger which is not executed properly.
The output of the second install is attached as logfile since thats
where this bug shows up.
Howto
** Attachment added: installprecise2.txt
https://bugs.launchpad.net/bugs/987207/+attachment/3099784/+files/installprecise2.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/987207
Public bug reported:
As requested by Micah Gersten:
When purging and installing puppetmaster-passenger again it wont start.
This is somehow due to a2enmod passenger which is not executed properly.
The output of the second install is attached as logfile since thats
where this bug shows up.
Howto
** Attachment added: installprecise2.txt
https://bugs.launchpad.net/bugs/987207/+attachment/3099784/+files/installprecise2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/987207
Title:
Hi James,
Thanks for your feedback!
1) The upstart script has been extended with daemon checks, checks on the
defaults file flags and also give error outputs. I added the puppet.conf
upstart script as attachment.
2) Since mongrel support will be deleted from debian
** Attachment added: puppetqd.conf
https://bugs.launchpad.net/ubuntu/q-series/+source/puppet/+bug/954368/+attachment/2909100/+files/puppetqd.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
** Attachment added: puppetmaster.conf
https://bugs.launchpad.net/ubuntu/q-series/+source/puppet/+bug/954368/+attachment/2909099/+files/puppetmaster.conf
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
** Attachment added: puppetmaster.conf
https://bugs.launchpad.net/ubuntu/q-series/+source/puppet/+bug/954368/+attachment/2909099/+files/puppetmaster.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: puppetqd.conf
https://bugs.launchpad.net/ubuntu/q-series/+source/puppet/+bug/954368/+attachment/2909100/+files/puppetqd.conf
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Hi James,
Thanks for your feedback!
1) The upstart script has been extended with daemon checks, checks on the
defaults file flags and also give error outputs. I added the puppet.conf
upstart script as attachment.
2) Since mongrel support will be deleted from debian
Public bug reported:
Upstart script for the puppet agent. See attachment for debdiff.
** Affects: puppet (Ubuntu)
Importance: Undecided
Status: New
** Tags: agent puppet upstart
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Patch added: debdiff for puppet
https://bugs.launchpad.net/bugs/954368/+attachment/2865153/+files/puppet_2.7.11-1ubuntu3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
Public bug reported:
Upstart script for the puppet agent. See attachment for debdiff.
** Affects: puppet (Ubuntu)
Importance: Undecided
Status: New
** Tags: agent puppet upstart
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Patch added: debdiff for puppet
https://bugs.launchpad.net/bugs/954368/+attachment/2865153/+files/puppet_2.7.11-1ubuntu3.debdiff
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/954368
Title:
This is fixed in bug 948983
** Changed in: puppet (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/948909
Title:
This is fixed in bug 948983
** Changed in: puppet (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/948909
Title:
puppetmaster-passenger does not
1: Correct, if /etc/puppet/puppet.conf has no [main] section with ssldir
set (to /var/lib/puppet/ssl) the puppetmaster-passenger package install
will use its default /etc/puppet/ssl path for the SSL variables in the
/etc/apache2/sites-available/puppetmaster vhost and the generated
certificate
James, check bug 948909 which i posted yesterday. Its about the a2enmod
headers
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/948983
Title:
puppetmaster-passenger default vhost has
Public bug reported:
How to reproduce:
echo abc /etc/puppet/puppet.conf
root@host:~# puppet config print
err: Could not parse /etc/puppet/puppet.conf: Could not match line abc at
/etc/puppet/puppet.conf:abc
root@host:~# aptitude install puppetmaster-passenger
The following NEW packages will
Adem, I can confirm that if it returns 0 on failure, which is really bad
behaviour. Its really sad that such simple things can cause so much
trouble.
For now the fastest fix is to see if err: is returned by puppet config
print in the postinst before even doing anything and if so the postinst
Ok, I think the puppet config print variable should be changed to puppet
--configprint variable:
# puppet config print abc; echo $?
err: Could not parse /etc/puppet/puppet.conf: Could not match line abc at
/etc/puppet/puppet.conf:bla
invalid parameter: abc
0
# puppet --configprint abc; echo $?
Yeah, that does the trick. Replace puppet config print in the postinst
with puppet --configprint and this bug can be resolved:
root@host:/etc# dpkg -i puppetmaster-passenger_2.7.11-1_all.deb
Selecting previously unselected package puppetmaster-passenger.
(Reading database ... 25803 files and
1: Correct, if /etc/puppet/puppet.conf has no [main] section with ssldir
set (to /var/lib/puppet/ssl) the puppetmaster-passenger package install
will use its default /etc/puppet/ssl path for the SSL variables in the
/etc/apache2/sites-available/puppetmaster vhost and the generated
certificate
James, check bug 948909 which i posted yesterday. Its about the a2enmod
headers
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/948983
Title:
puppetmaster-passenger default vhost has wrong
Public bug reported:
How to reproduce:
echo abc /etc/puppet/puppet.conf
root@host:~# puppet config print
err: Could not parse /etc/puppet/puppet.conf: Could not match line abc at
/etc/puppet/puppet.conf:abc
root@host:~# aptitude install puppetmaster-passenger
The following NEW packages will
Adem, I can confirm that if it returns 0 on failure, which is really bad
behaviour. Its really sad that such simple things can cause so much
trouble.
For now the fastest fix is to see if err: is returned by puppet config
print in the postinst before even doing anything and if so the postinst
Ok, I think the puppet config print variable should be changed to puppet
--configprint variable:
# puppet config print abc; echo $?
err: Could not parse /etc/puppet/puppet.conf: Could not match line abc at
/etc/puppet/puppet.conf:bla
invalid parameter: abc
0
# puppet --configprint abc; echo $?
Yeah, that does the trick. Replace puppet config print in the postinst
with puppet --configprint and this bug can be resolved:
root@host:/etc# dpkg -i puppetmaster-passenger_2.7.11-1_all.deb
Selecting previously unselected package puppetmaster-passenger.
(Reading database ... 25803 files and
Public bug reported:
When installing puppetmaster-passenger the install will not finish
without errors. After doing some research the problem is because apache2
mod_headers is not enabled.
Output from install:
To activate the new configuration, you need to run:
service apache2 reload
Syntax
Public bug reported:
After a clean install of puppetmaster-passenger on 12.04 the vhost
/etc/apache2/sites-available/puppetmaster is wrong:
1: SSL certificates for puppetmaster on ubuntu are not in /etc/puppet/ssl but
in /var/lib/puppet/ssl
2: Rack application for puppetmaster on ubuntu is not
Public bug reported:
When installing puppetmaster-passenger the install will not finish
without errors. After doing some research the problem is because apache2
mod_headers is not enabled.
Output from install:
To activate the new configuration, you need to run:
service apache2 reload
Syntax
Public bug reported:
After a clean install of puppetmaster-passenger on 12.04 the vhost
/etc/apache2/sites-available/puppetmaster is wrong:
1: SSL certificates for puppetmaster on ubuntu are not in /etc/puppet/ssl but
in /var/lib/puppet/ssl
2: Rack application for puppetmaster on ubuntu is not
(0.8.6-3) unstable; urgency=low
* Added dovecot section to Debian's jail.conf. Thanks to Laurent
Léonard (Closes: #655182)
* init.d script now returns non-0 exit codes upon status command
with not running / failed to connect server. Thanks to
Glenn Aaldering for the patch
Applies to
https://bugs.launchpad.net/ubuntu/+source/fail2ban/+bug/920995
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/931338
Title:
Sync fail2ban 0.8.6-3 (universe) from Debian unstable (main)
This was patched in debian upstream:
https://github.com/fail2ban/fail2ban/pull/36
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/920995
Title:
SysV status script returns the wrong exit code when
** Changed in: fail2ban (Ubuntu)
Assignee: (unassigned) = Glenn Aaldering (glenn-openvideo)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/920995
Title:
SysV status script returns the wrong
Public bug reported:
Running the status command on the fail2ban sysv init script returns the
wrong exit code:
[Precise]
# /etc/init.d/fail2ban status
* Status of authentication failure monitor
Public bug reported:
SysV status script returns the wrong exit code when postgresql is not
running:
[Precise]
# /etc/init.d/postgresql status
Running clusters:
# echo $?
0
This seems to work ok in Lucid:
[Lucid]
# /etc/init.d/postgresql-8.4 status
Running clusters:
# echo $?
3
** Affects:
Public bug reported:
SysV status script returns the wrong exit code when varnish is not
running:
[Lucid]
# /etc/init.d/varnish status
* varnishd is not running
# echo $?
0
This seems to work properly in Precise:
[Precise]
# /etc/init.d/varnish status
* varnishd is not running
# echo $?
3
**
Very annoying bug. Lets fix this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/218965
Title:
preseeding hostname doesn't work in a network install
To manage notifications about this bug go to:
Public bug reported:
Binary package hint: gitosis
If a user on the system exists with the word gitosis in it the default
install of gitosis will fail. In my case i already had user gitosistest.
Im not exactly sure how it is matched.
Probably most people dont have a user on the system already
44 matches
Mail list logo
