users July 2012

users@lists.fedoraproject.org

252 participants
266 discussions

Trolling (Was: Message when running yum update)
by Daniel 01 Jul '12

01 Jul '12

On 07/01/2012 13:14:26 UTC, Reindl Harald sayed: > do you not realize that this guy is replying ANY message of > me to the list with idiotic bullshit even for threads nobody > spoke to him? I don't know why Heinz Diehl seems not to recognize what is happening. I also don't know whether n2xssvv.g02gfr12930 is deliberately trolling you is is just BFC. But the correct response at this stage would not be to keep replying to n2xssvv.g02gfr12930; the correct response would be to contact one or two of the list maintainers <URL:https://admin.fedoraproject.org/mailman/listinfo/users> about the matter.

1 0

Fail to start bacula director with systemctl.
by Erik P. Olsen 01 Jul '12

01 Jul '12

When migrating to fedora 16 (from 14) I have to start bacula using systemctl. It works fine with the client and storage daemons but the director service fails. systemctl status bacula-<daemon> shows: [root@epohost ~]# systemctl status bacula-dir.service bacula-dir.service - Bacula-Director, the Backup-server Loaded: loaded (/lib/systemd/system/bacula-dir.service; enabled) Active: failed since Fri, 29 Jun 2012 23:09:35 +0200; 1min 9s ago Process: 1781 ExecStart=/usr/sbin/bacula-dir -f $OPTS -c $CONFIG -u $DIR_USER -g $DIR_GROUP (code=exited, status=1/FAILURE) Process: 1778 ExecStartPre=/usr/sbin/bacula-checkconf $CONFIG (code=exited, status=0/SUCCESS) CGroup: name=systemd:/system/bacula-dir.service [root@epohost ~]# systemctl status bacula-sd.service bacula-sd.service - Bacula-StorageDaemon, the storage-server Loaded: loaded (/lib/systemd/system/bacula-sd.service; enabled) Active: active (running) since Fri, 29 Jun 2012 23:09:27 +0200; 1min 42s ago Process: 1205 ExecStartPre=/usr/sbin/bacula-checkconf $CONFIG (code=exited, status=0/SUCCESS) Main PID: 1219 (bacula-sd) CGroup: name=systemd:/system/bacula-sd.service └ 1219 /usr/sbin/bacula-sd -f -c /etc/bacula/bacula-sd.co... [root@epohost ~]# systemctl status bacula-fd.service bacula-fd.service - Bacula-FileDaemon, a Backup-client Loaded: loaded (/lib/systemd/system/bacula-fd.service; enabled) Active: active (running) since Fri, 29 Jun 2012 23:09:27 +0200; 1min 55s ago Process: 1196 ExecStartPre=/usr/sbin/bacula-checkconf $CONFIG (code=exited, status=0/SUCCESS) Main PID: 1214 (bacula-fd) CGroup: name=systemd:/system/bacula-fd.service └ 1214 /usr/sbin/bacula-fd -f -c /etc/bacula/bacula-fd.co... Can somebody decipher what is wrong or perhaps suggest a way to diagnose the problem? Starting bacula-dir manually works fine. Maybe this is for the bacula community to answer but I've started here since it may a failure in the rpm package. -- Erik

4 10

Cannot find valid baseurl for rpmfusion repo
by Mark Haney 01 Jul '12

01 Jul '12

I've googled this a couple of times, but can't seem to find a straight answer on this problem. I installed the rpmfusion repos both with the GUI and from the CLI and I get this same problem, 'Cannot find valid baseurl'. Any ideas? -- Mark Haney Software Developer/Consultant AB Emblem markh(a)abemblem.com Linux marius.homelinux 3.4.2-1.fc16.x86_64 GNU/Linux

5 17

kernel:[193562.569274] [Hardware Error]: cache level: L3/GEN, mem/io: MEM, mem-tx: RD, part-proc: RES (no timeout)
by Gary Artim 30 Jun '12

30 Jun '12

Since upgrading to fc17 been getting: [192963.306958] [Hardware Error]: cache level: L3/GEN, mem/io: MEM, mem-tx: RD, part-proc: SRC (no timeout) [193262.911077] [Hardware Error]: CPU:4 MC4_STATUS[Over|CE|MiscV|-|AddrV|CECC]: 0xdc20c000dd080813 [193262.916531] [Hardware Error]: MC4_ADDR: 0x000000081f2e2020 [193262.921903] [Hardware Error]: Northbridge Error (node 1): DRAM ECC error detected on the NB. [193262.927322] EDAC amd64 MC1: CE ERROR_ADDRESS= 0x81f2e2020 [193262.932657] EDAC MC1: CE page 0x81f2e2, offset 0x20, grain 0, syndrome 0xdd41, row 3, channel 1, label "": amd64_edac [193262.938047] [Hardware Error]: cache level: L3/GEN, mem/io: MEM, mem-tx: RD, part-proc: SRC (no timeout) [193562.542225] [Hardware Error]: CPU:4 MC4_STATUS[Over|CE|MiscV|-|AddrV|CECC]: 0xdc61c000bb080a13 [193562.547766] [Hardware Error]: MC4_ADDR: 0x000000081f2f1370 [193562.553153] [Hardware Error]: Northbridge Error (node 1): DRAM ECC error detected on the NB. [193562.558564] EDAC amd64 MC1: CE ERROR_ADDRESS= 0x81f2f1370 [193562.563895] EDAC MC1: CE page 0x81f2f1, offset 0x370, grain 0, syndrome 0xbbc3, row 3, channel 1, label "": amd64_edac [193562.569274] [Hardware Error]: cache level: L3/GEN, mem/io: MEM, mem-tx: RD, part-proc: RES (no timeout) Could be a real h/w problem or related to the upgrade? Advise welcomed...Any kernel boot switches that may help. Seem to run for a while just fine, then start periodically getting these messages. Have not run memtest+ yet, plan to shortly, but sound like L3 cache, would this show up in memtest? Thanks for advise!

1 0

k3b and create image
by JD 30 Jun '12

30 Jun '12

I used k3b to copy the image of an audio cd. It produced files like Track01.wav .... Track16.wav and it also produced a file simply with the title of the audio cd, and without extensions and it is 803066400 bytes large. Running $ file 'Into The Unknown' Into The Unknown: data The file is quite larger than the 704MB max (with overburn) that a CD can hold. This file is 100MB larger than that. So, how can I use this file? I was hoping it would be in a format that could be used by any of the plethora of media players in linux. mplayer failed to open it.

4 7

Re: what on earth is firefox up to?
by Daniel 30 Jun '12

30 Jun '12

On 06/30/2012 07:17 PM PM, Tom Horsley sayed: > Every time I start firefox after recent updates, top > shows it periodically taking up to 50% of the CPU > even if I'm just looking at a simple page of plain > html (no scripts, not even any images) on my local > web server. > > This is ff 13.0.1 on x86_64 fedora 17. > > Any clues? Anyone see anything similar? Basically the same thing here -- FF 13.0.1 on fedora core 17 x86_64 -- except that CPU usage isn't maxxing at 50%; it sometimes climbs a bit above that. Haven't started my i686 machine to see whether the same behavior occurs thereupon.

1 0

Jump to page: