Well, I reported the issue because the sarg monthly report was never
made in a pristine installation. In the research I found that the
access.log file was truncated in a period of time (daily) which is not
appropriate for a monthly report, nor even weekly reports. Even though
sarg scripts are
Public bug reported:
accident d'installation récurrent n'empéchant pas a ce jour le bon
fonctionnement. Courage et merci.
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: setserial 2.17-48ubuntu0.1
ProcVersionSignature: Ubuntu 3.19.0-22.22-generic 3.19.8-ckt1
Uname: Linux
Public bug reported:
i don't kown
ProblemType: Package
DistroRelease: Ubuntu 15.04
Package: openhpid 2.14.1-1.3ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-14.14-generic 3.19.3
Uname: Linux 3.19.0-14-generic x86_64
ApportVersion: 2.17.2-0ubuntu1
AptOrdering:
libopenhpi2: Install
openhpid:
In the mean time I migrated to Ubuntu Server 13.04. DiskMonitor is doing
its job now and since I am the only affected I will mark this bug as
invalid.
** Changed in: powernap (Ubuntu)
Status: Triaged = Invalid
--
You received this bug notification because you are a member of Ubuntu
Hi Andres,
I tested the algorithm from your link. Running the script under my user account
results in the status message Disk is active whether or not the drive is
spinning.
However, the script is working correctly when run as root. This is off coarse
because hdparm needs to be invoked as
And here a link to the requested log file. Verbosity was set to 3.
http://paste.ubuntu.com/5577621/
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to powernap in Ubuntu.
https://bugs.launchpad.net/bugs/1131713
Title:
DiskMonitor not
Note for the supplied /etc/powernap/config file:
Line init = ^/sbin/init under [Process Monitor] should be commented out.
Line threshold = 0under [LoadMonitor] should be changed to threshold = n.
I changed both parameters to prevent PowerNap to take any action for the
time being.
--
You
** Description changed:
I am unable to get the DiskMonitor to work on my server. Powernap still
wants to suspend when the disks are spinning.
Steps to reproduce:
1. sudo apt-get -y install powernap
2. sudo hdparm -S 60 /dev/sda (Sets spindown to 5 minutes for drive sda)
- 3. After 10
apport information
** Tags added: apport-collected precise
** Description changed:
I am unable to get the DiskMonitor working on my server. Powernap still
wants to suspend when the disks are spinning.
I have added the options below to the [DiskMonitor] section of
/etc/powernap/config
apport information
** Attachment added: modified.conffile..etc.powernap.config.txt
https://bugs.launchpad.net/bugs/1131713/+attachment/3547519/+files/modified.conffile..etc.powernap.config.txt
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is
** Description changed:
I am unable to get the DiskMonitor working on my server. Powernap still
wants to suspend when the disks are spinning.
- I have added the options below to the [DiskMonitor] section of
/etc/powernap/config and restarted the service.
- sda = y
- sdb = y
- sdd = y
-
Public bug reported:
I am unable to get the DiskMonitor working on my server. Powernap still
wants to suspend when the disks are spinning.
I have added the options below to the [DiskMonitor] section of
/etc/powernap/config and restarted the service.
sda = y
sdb = y
sdd = y
** Affects: powernap
Public bug reported:
When using dhclient to renew IP, /etc/dhcp3/dhclient-enter-hooks.d/samba is
called.
Unfortunatly, this script use an old method to reload smbd
(/usr/sbin/invoke-rc.d smbd reload).
This call give some error messages.
papounet@amd8papou:~$ sudo dhclient
Rather than invoking
Public bug reported:
Binary package hint: samba
Bonjour,
C'est lors de la mise à jour que le problème s'est présenté.
Merci
Alain
ProblemType: Package
Architecture: amd64
DistroRelease: Ubuntu 9.04
ErrorMessage: le sous-processus post-installation script a retourné une erreur
de sortie d'état
** Attachment added: Dependencies.txt
https://bugs.launchpad.net/bugs/640553/+attachment/1593985/+files/Dependencies.txt
** Attachment added: DpkgTerminalLog.gz
https://bugs.launchpad.net/bugs/640553/+attachment/1593986/+files/DpkgTerminalLog.gz
--
package samba-common
I'm encountering a similar enough problem that I think it is the same.
Fresh Ubuntu 10.04 server, installing mysql-
server-5.1_5.1.41-3ubuntu12_amd64.deb (and dependencies) from official
repos, the install seemed to work but mysql doesn't start. 'start mysql'
just shows start: Job failed to start
I can't help you anymore, i'm not a specialist of linux. Sorry and
thanks.
--
krb5-admin-server fails during install
https://bugs.launchpad.net/bugs/44402
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to krb5 in ubuntu.
--
Yes. I tried incrementing the log level in smb.conf and rebooting, but
the information logged remains the same, until reaching log level 8 or
higher. Then nmbd suddenly appears to start normally. There appears to
be something racy going on here.
--
nmbd dies on startup when network interfaces
For a possible workaround, maybe we could look at this bug (note: not
the same problem, and no longer available in Launchpad):
https://lists.ubuntu.com/archives/ubuntu-server-
bugs/2009-May/012893.html
Personally I would prefer something in /etc/network/if-*.d/ which would
also serve users
Can someone who is seeing this problem in Ubuntu 9.10 please send the
following:
- a copy of /var/log/samba/log.nmbd showing the boot-time failure
- a copy of your /etc/samba/smb.conf
Here you go. I set log level = 3 (possibly overkill) to make an error
show up, for otherwise nmbd seems to
And here the smb.conf (not changed AFAIK except for log level = 3)
** Attachment added: smb.conf
http://launchpadlibrarian.net/35955631/smb.conf
--
nmbd dies on startup when network interfaces are not up yet
https://bugs.launchpad.net/bugs/462169
You received this bug notification because
21 matches
Mail list logo
