I followed post #21 change and solved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448924
Title:
watchdogd doesn't start on boot
To manage notifications about this bug go to:
Please review the SRU process here.
https://wiki.ubuntu.com/StableReleaseUpdates
When it lands in -proposed, your help in the verification process is most
welcomed.
On Thu, May 4, 2017 at 10:46 AM, Алексей wrote:
> okay, is there any ETA for SRU process to be finished?
> We
okay, is there any ETA for SRU process to be finished?
We can fix this by hands while fix not released, but we dont like this way
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448924
Title:
It's not been released. I've just started the SRU process for getting it
into xenial-updates.
If you want to test, you can try out the package from the PPA:
ppa:raharper/bugfixes
On Thu, May 4, 2017 at 4:27 AM, Алексей wrote:
> Ryan, but I couldnt find this version in
Ryan, but I couldnt find this version in repos:
# cat /etc/apt/sources.list
deb http://mirror.yandex.ru/ubuntu xenial main restricted universe multiverse
deb http://mirror.yandex.ru/ubuntu xenial-security main restricted universe
multiverse
deb http://mirror.yandex.ru/ubuntu xenial-updates main
** Description changed:
+ [Impact]
+
+ * The watchdog service in Xenial does not start automatically even after
+being configured. This makes the service not function reliably.
+
+This affects the 5.14 release in Xenial only and is already fixed in
+5.15 included in the
+1 is there any chances to get backport for xenial?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448924
Title:
watchdogd doesn't start on boot
To manage notifications about this bug go to:
Encountered this today on an up-to-date xenial.
Quite scary to see such a critical service not being functional on a up-
to-date LTS distro.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448924
On Tue, Jun 28, 2016 at 1:01 PM, Alexander E. Patrakov <
1448...@bugs.launchpad.net> wrote:
> The proposed modification of the service file works. It works both with
> default.target and with multi-user.target.
>
Thanks for testing.
The target selection was based on what's upstream in the
The proposed modification of the service file works. It works both with
default.target and with multi-user.target.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448924
Title:
watchdogd doesn't
I will test it later today, but - why are you using default.target
instead of multi-user.target?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448924
Title:
watchdogd doesn't start on boot
To
On Mon, Jun 13, 2016 at 8:18 PM, David Kowis wrote:
> Sorry for the noise on this bug! It turns out I'm simply not waiting
> long enough for it to come up. It is being started on boot, and
> everything is working like I expect, just isn't showing up.
>
>
> I do still have the
On Mon, Jun 13, 2016 at 8:10 PM, David Kowis wrote:
> Also, I've grabbed and installed the 5.15-1 .dpkg. systemctl reports
> that it's enabled, but it never starts on boot. Checking right after
> boot yields this:
>
> ```
> root@hylden:~# systemctl status watchdog
> ●
David, how long did you have to wait? For me, it's still not started,
even though the uptime is 7 minutes. And I don't see how it is supposed
to be started, given that nothing pulls it in (i.e. it is not WantedBy
anything).
--
You received this bug notification because you are a member of Ubuntu
Sorry for the noise on this bug! It turns out I'm simply not waiting
long enough for it to come up. It is being started on boot, and
everything is working like I expect, just isn't showing up.
I do still have the question about when it'll make it into a Xenial-updates
repo, though.
Thanks, and
Also, I've grabbed and installed the 5.15-1 .dpkg. systemctl reports
that it's enabled, but it never starts on boot. Checking right after
boot yields this:
```
root@hylden:~# systemctl status watchdog
● watchdog.service - watchdog daemon
Loaded: loaded (/lib/systemd/system/watchdog.service;
Forgive my ignorance, but is this going to make it into a standard
xenial updates repo?
It's very broke as it stands right now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448924
Title:
This bug was fixed in the package watchdog - 5.15-1
---
watchdog (5.15-1) unstable; urgency=medium
* New upstream version.
* Updated Dutch translation. (Closes: #772760)
* Updated Russian translation. (Closes: #776125)
* Updated Japanese translation. (Closes: #815857)
*
On Mon, Apr 18, 2016 at 4:05 PM, Paul Crawford <1448...@bugs.launchpad.net>
wrote:
> I will try to look tomorrow or so at the proposed fix.
> Have you checked if it is still loaded OK following a reboot?
>
Yes, it continues to work after reboot.
It's best if you configure /etc/default/watchdog
I will try to look tomorrow or so at the proposed fix.
Have you checked if it is still loaded OK following a reboot?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448924
Title:
watchdogd doesn't
I've uploaded a version of watchdog with this debdiff attached to my
ppa:
ppa:raharper/bugfixes
Please give a go and see if that resolves the starting on boot issue.
I've verified this fix myself under QEMU with a Xenial cloud image:
# create some user-data for easy login
% cat user-data
The attachment "fix-watchdog-service.debdiff" seems to be a debdiff.
The ubuntu-sponsors team has been subscribed to the bug report so that
they can review and hopefully sponsor the debdiff. If the attachment
isn't a patch, please remove the "patch" flag from the attachment,
remove the "patch"
Pull in two fixes from upstream debian 5.15 release which resolves the
service starting issue.
Note, users upgrading will need to run:
systemctl enable watchdog
after upgrading to ensure watchdog service is enabled (new installers of
the package will have the service enabled by default).
**
I tested the proposed fix from comment #7 on bug #1535854 but it did not
work for that system (16.04) :(
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448924
Title:
watchdogd doesn't start on boot
This is probably the same problem as bug #1535854 thought there could be
a number of related factors, for example bug #1535840 for module
loading.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448924
Just tested it with the current Wily version and the bug still persists.
So I had a look into the systemd service script and I was able to fix it
for myself, simply copy this to file
/lib/systemd/system/watchdog.service :
[Unit]
Description=watchdog daemon
Conflicts=wd_keepalive.service
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: watchdog (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448924
Title:
On some systems, watchdog not starting at boot can lead to infinite
system reset loops.
Better behaved hardware watchdogs starts the counter on first open/write
to /dev/watchdog and thus not starting on boot is not fatal, but will
cause system lockups to go undetected.
--
You received this bug
Tried that before but I get the following messages :
Synchronizing state for watchdog.service with sysvinit using update-rc.d...
Executing /usr/sbin/update-rc.d watchdog defaults
Executing /usr/sbin/update-rc.d watchdog enable
The unit files have no [Install] section. They are not meant to be
** Changed in: watchdog (Ubuntu)
Status: Incomplete = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448924
Title:
watchdogd doesn't start on boot
To manage notifications about this bug
Medium: Problem with non-essential hardware component
(With a workaround of restarting the service).
Arne: I suggest trying a systemctl enable watchdogdto see if it
starts at the next boot and remembers it.
** Changed in: watchdog (Ubuntu)
Importance: Undecided = Medium
--
You received
The problem happens on several KVM machines with (virtual) Intel 6300ESB
WatchDog. Here's the driver load log from dmesg :
[37539.207098] i6300esb: Intel 6300ESB WatchDog Timer Driver v0.05
[37539.210190] i6300esb: initialized (0xc907c000). heartbeat=30 sec
(nowayout=0)
I've attached
Hello,
what are your hardware settings?
Greets
** Changed in: watchdog (Ubuntu)
Status: New = Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1448924
Title:
watchdogd doesn't
33 matches
Mail list logo