[Bug 1627068] [NEW] Uninstalling package do not disable module making PHP cron to crash
Public bug reported:
Hello,
Last day we installed the package php5-geoip, enabled it and then, few days
after that, removed it.
We then had an issue, the crontab, /etc/cron.d/php5, setup by the package
php5-common, crashed.
In order to prevent this issue, we are wondering if it could be possible
to update the uninstall hook in order to disable the GeoIP extension
when the package is removed?
Best Regards,
David Fischer
Here is the error:
Cron [ -x /usr/lib/php5/maxlifetime ] && [ -d /var/lib/php5 ] && find
/var/lib/php5/ -depth -mindepth 1 -maxdepth 1 -type f -cmin
+$(/usr/lib/php5/maxlifetime) ! -execdir fuser -s {} 2>/dev/null \; -delete
PHP Warning: PHP Startup: Unable to load dynamic library
'/usr/lib/php5/20090626/geoip.so' - /usr/lib/php5/20090626/geoip.so: cannot
open shared object file: No such file or directory in Unknown on line 0
** Affects: php-geoip (Ubuntu)
Importance: Undecided
Status: New
** Tags: cleanup
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1627068
Title:
Uninstalling package do not disable module making PHP cron to crash
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/php-geoip/+bug/1627068/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1277894] Re: GExiv2 python wrapper broken
Working with Python 2.7, not Python 3.3:
python3 -c from gi.repository.GExiv2 import Metadata;
Metadata(path='my_image.png')
In Python 3.3:
Traceback (most recent call last):
File stdin, line 1, in module
TypeError: gobject `GExiv2Metadata' doesn't support property `path'
A workaround:
python3 -c from gi.repository.GExiv2 import Metadata; m =
Metadata(); m.open_path('my_image.png')
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1277894
Title:
GExiv2 python wrapper broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gexiv2/+bug/1277894/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1204302] Re: fails to bootstrap, returns error: no reachable servers
I also think that the debian package of juju-core is missing a dependency (mongodb). Installing it manually solved this. 2013-08-15 09:03:40 INFO juju open.go:69 state: opening state; mongo addresses: [localhost:37017]; entity 2013-08-15 09:03:40 ERROR juju open.go:89 state: connection failed, will retry: dial tcp 127.0.0.1:37017: connection refused (...) Thanks, David -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1204302 Title: fails to bootstrap, returns error: no reachable servers To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1204302/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1204302] Re: fails to bootstrap, returns error: no reachable servers
I also think that the debian package of juju-core is missing a dependency (mongodb). Installing it manually solved this. 2013-08-15 09:03:40 INFO juju open.go:69 state: opening state; mongo addresses: [localhost:37017]; entity 2013-08-15 09:03:40 ERROR juju open.go:89 state: connection failed, will retry: dial tcp 127.0.0.1:37017: connection refused (...) Thanks, David -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1204302 Title: fails to bootstrap, returns error: no reachable servers To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1204302/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1183508] [NEW] A command to scale-down a service safely.
Public bug reported: My question is the following (maybe a feature request, I do no how to create one) : Imagine a service like GlusterFS requiring to migrate data from removed bricks before shuting-down the node(s) that will be removed from the cluster. gluster/0 with volume1 gluster/1 with volume2 (replica=2) gluster/2 with volume2 (replica=2) How exactly juju triggers the hooks of the units of that service ? I imagine that all units are aware of the departure of gluster/2 if we remove gluster/2. A good feature will be to have, as user, a way to express our desire to scale-down the service without specifying one particular unit, unlike juju remove-unit. Another will be, as unit of the service, a way to decide to cancel or warn the user helped by juju. For example, if the user uses juju remove- unit gluster/0 it will loose all data of volume1 ! Kind Regards, David ** Affects: juju (Ubuntu) Importance: Undecided Status: New ** Tags: juju remove-unit ** Summary changed: - A command to scale-out a service safely. + A command to scale-down a service safely. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1183508 Title: A command to scale-down a service safely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1183508/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1183508] [NEW] A command to scale-down a service safely.
Public bug reported: My question is the following (maybe a feature request, I do no how to create one) : Imagine a service like GlusterFS requiring to migrate data from removed bricks before shuting-down the node(s) that will be removed from the cluster. gluster/0 with volume1 gluster/1 with volume2 (replica=2) gluster/2 with volume2 (replica=2) How exactly juju triggers the hooks of the units of that service ? I imagine that all units are aware of the departure of gluster/2 if we remove gluster/2. A good feature will be to have, as user, a way to express our desire to scale-down the service without specifying one particular unit, unlike juju remove-unit. Another will be, as unit of the service, a way to decide to cancel or warn the user helped by juju. For example, if the user uses juju remove- unit gluster/0 it will loose all data of volume1 ! Kind Regards, David ** Affects: juju (Ubuntu) Importance: Undecided Status: New ** Tags: juju remove-unit ** Summary changed: - A command to scale-out a service safely. + A command to scale-down a service safely. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1183508 Title: A command to scale-down a service safely. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju/+bug/1183508/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 994779] Re: changing the IP address of the maas server requires a reinstall
I do no if this is the right answer to your question but I faced the same kind of problem : The MaaS web user interface became unrecheable after changing the IP address of my controller. The solution was to reconfigure a lot of MaaS related packages : dpkg --get-selections | grep maas Here is the output : maas install maas-cliinstall maas-cluster-controllerinstall maas-common install maas-region-controller install python-django-maas install python-maas-clientinstall python-maas-provisioningserver install I reconfigured the packages : $ sudo dpkg-reconfigure maas-region-controller $ sudo dpkg-reconfigure maas-cluster-controller $ sudo ... $ sudo reboot ... All works fine now ! Hope it helps. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/994779 Title: changing the IP address of the maas server requires a reinstall To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/994779/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 994779] Re: changing the IP address of the maas server requires a reinstall
I do no if this is the right answer to your question but I faced the same kind of problem : The MaaS web user interface became unrecheable after changing the IP address of my controller. The solution was to reconfigure a lot of MaaS related packages : dpkg --get-selections | grep maas Here is the output : maas install maas-cliinstall maas-cluster-controllerinstall maas-common install maas-region-controller install python-django-maas install python-maas-clientinstall python-maas-provisioningserver install I reconfigured the packages : $ sudo dpkg-reconfigure maas-region-controller $ sudo dpkg-reconfigure maas-cluster-controller $ sudo ... $ sudo reboot ... All works fine now ! Hope it helps. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/994779 Title: changing the IP address of the maas server requires a reinstall To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/994779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 649182] Re: Asrock X58 IDE / PATA controller doesn't work
** Bug watch added: Novell/SUSE Bugzilla #649997 https://bugzilla.novell.com/show_bug.cgi?id=649997 ** Also affects: linux (openSUSE) via https://bugzilla.novell.com/show_bug.cgi?id=649997 Importance: Unknown Status: Unknown -- Asrock X58 IDE / PATA controller doesn't work https://bugs.launchpad.net/bugs/649182 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
