Re: empty messages from fedora users list.

On 03/15/2018 08:51 AM, William Mattison wrote: Tried it: bash.4[~]: export MOZ_LOG_FILE=/[myhome]/thunderbird/log bash.5[~]: export MOZ_LOG=IMAP:5,timestamp Looking through the source code, I found that the environment variables used are different now. You want "NSPR_LOG_FILE" and

Re: sound problem

On Thu, 15 Mar 2018 11:03:32 +0100 François Patte wrote: > > After 3, when sound is working, open pavucontrol, go to the output > > devices tab, and click the green checkmark on the device that you > > want pulseaudio to start with. > > That is what I do

Re: /etc/nsswitch.conf

I recently had to sit down and figure this out. Here is my understanding. The mdns4_minimal will ONLY do a search if the hostname ends in .local. If the hostname does not end in .local then mdns4_minimal does not make a search at all and so NOTFFOUND is false because it didn't look for the

[389-users] Re: Cannot login to admin server after last update

On 03/15/2018 04:11 PM, Julian Kippels wrote: > Am Thu, 15 Mar 2018 12:00:06 -0400 > schrieb Mark Reynolds : > >> On 03/15/2018 11:36 AM, Julian Kippels wrote: >>> Hi, >>> >>> since the last update (using RHEL 7, updated from 389-ds-1.3.6.1-21 >>> to 389-ds-1.3.6.1-28) I

Re: empty messages from fedora users list.

On 03/15/2018 08:51 AM, William Mattison wrote: What I was suggesting... KSysGuard shows that yahoo feeds data to Thunderbird in very teeny chunks. A message with an attached photo took about an hour to download yesterday. I also access my e-mail from multiple workstation accounts and

Re: F19 RAID1 drive died - what if it was sda that died?

/boot is on /: [0:root@elmo raid]$ df Filesystem  Size  Used Avail Use% Mounted on /dev/md2    1.9T  834G 1021G  45% / /dev/sdc2   3.6T  2.3T  1.4T  63% /bacula dos partition table (/dev/sdb is the same): [0:root@elmo raid]$ fdisk -l /dev/sda Disk /dev/sda: 1.8 TiB, 2000398934016

[389-users] Re: Cannot login to admin server after last update

On 03/15/2018 11:36 AM, Julian Kippels wrote: > Hi, > > since the last update (using RHEL 7, updated from 389-ds-1.3.6.1-21 to > 389-ds-1.3.6.1-28) I cannot login as user admin in the administration > console anymore. > > Looking at the logs I see this error message popping up every time I > try

Re: F19 RAID1 drive died - what if it was sda that died?

On Thursday 15 March 2018 15:43:49 Tim wrote: > I thought with RAID1 being "all drives identical," and that unless you > were using yet another drive to boot from (separate from your raid), > that each drive would have a boot partition on it. Following that > train of thought, if your controller

Re: empty messages from fedora users list.

> What I was suggesting... KSysGuard shows that yahoo feeds data to Thunderbird in very teeny chunks. A message with an attached photo took about an hour to download yesterday. I also access my e-mail from multiple workstation accounts and operating systems. So some time ago, I set all my

Re: F19 RAID1 drive died - what if it was sda that died?

Allegedly, on or about 15 March 2018, Gary Stainburn sent: > From what I understand, and from past experience of when software > RAID1 setups have failed, it isn't possible to boot using the second > drive. > > Ideally, in that situation I would want to make the second drive the > first drive,

[389-users] Cannot login to admin server after last update

Hi, since the last update (using RHEL 7, updated from 389-ds-1.3.6.1-21 to 389-ds-1.3.6.1-28) I cannot login as user admin in the administration console anymore. Looking at the logs I see this error message popping up every time I try to log in since then: [Thu Mar 15 13:09:35.046721 2018]

Re: F19 RAID1 drive died - what if it was sda that died?

Part of the reason that this recover seems to have gone well is that the system booted up and gave me access to everything. How would I have been able to complete the recovery if it had been the boot device that had failed? From what I understand, and from past experience of when software

Re: F19 RAID1 drive died

On Thursday 15 March 2018 14:50:07 Bill Shirley wrote: > > If that doesn't work try: 'mdadm /dev/md124 --re-add /dev/sdb2'. > > Bill Thanks for this Bill, but I did sgdisk /dev/sda -R /dev/sdb sgdisk -G /dev/sdb followe by mdadm /dev/md124 --manage --add /dev/sdb2 mdadm /dev/md125 --manage

Re: F19 RAID1 drive died

On 3/15/2018 10:28 AM, Gary Stainburn wrote: On Thursday 15 March 2018 13:59:39 Juan Martinez wrote: Hi Gary, You should use parted instead of fdisk to create the GPT and its partitions. It should be able to handle larger partitions than fdisk. Are you using mdadm for the RAID1 array? I

Re: F19 RAID1 drive died

Would have been good if I'd actually pasted the commands: sgdisk /dev/sda -R /dev/sdb sgdisk -G /dev/sdb ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org

Re: F19 RAID1 drive died

On Thursday 15 March 2018 13:59:39 Juan Martinez wrote: > Hi Gary, > > You should use parted instead of fdisk to create the GPT and its > partitions. It should be able to handle larger partitions than fdisk. > > Are you using mdadm for the RAID1 array? I ended up using the following to clone the

Re: F19 RAID1 drive died

On Thu, Mar 15, 2018 at 12:30:14PM +, Gary Stainburn wrote: Hi all, Yesterday one of the HDD's in a F19 (yes I know) server died. I found this out when the server would not reboot (45miles away from where I was too :( ) The only way the server would boot was if I disconnected the drive,

Re: Is there a way to get something into a Fedora How To list?

On Wed, Mar 14, 2018 at 12:54:54PM -0700, ToddAndMargo wrote: > https://kbpdfstudio.qoppa.com/how-to-set-up-your-scanner-to-work-with-sane-and-pdf-studio-under-fedora-27-linuxs-systemd/ > > I inquired over on the sane mailing list as to getting it into > their how to's but they ignored me. Is

Re: Alternative of Workrave

On Sat, Mar 3, 2018 at 11:15 AM Robbi Nespu wrote: Tried with breakRSI (It importing lot of KDE library to my gnome machine) but auto start failed. Also tried Stretchly, it more modern but I don't know to to set the time fro micro break. I ended using the workrave

F19 RAID1 drive died

Hi all, Yesterday one of the HDD's in a F19 (yes I know) server died. I found this out when the server would not reboot (45miles away from where I was too :( ) The only way the server would boot was if I disconnected the drive, connected to ATA0 /dev/sdb. I have now replaced the drive with

Re: Wow, KVM is great :-)

On Wed, 2018-03-14 at 16:57 -0700, Samuel Sieb wrote: > On 03/14/2018 04:17 PM, Patrick O'Callaghan wrote: > > I do that literally every day, for Windows gaming. It took some effort > > to set up but it works a treat. A good starting point is: > > > >

Re: sound problem

Le 14/03/2018 à 19:36, stan a écrit : > On Wed, 14 Mar 2018 10:36:33 +0100 > François Patte wrote: > >> When I log-in, sound is deactivated and I have to manually start it, >> doing: > > Are you sure sound is deactivated? Is it possible it is trying to use

Re: No network on first try

On 03/15/18 04:49, Martin Wagner wrote: > I've got a Fedora 27 desktop that has a slight network problem. > > I'm using VPN and I used nm-connection-editor to configure it so that > the VPN activates when eno1 activates. That worked fine in Fedora 26. > But after upgrade to Fedora 27 the network

Re: No network on first try

On 03/14/2018 11:29 PM, Martin Wagner wrote: TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=no IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes IPV6_FAILURE_FATAL=no IPV6_ADDR_GEN_MODE=stable-privacy NAME="Profile 2" UUID= ONBOOT=yes

Re: No network on first try

On Wed, 2018-03-14 at 18:00 -0700, toddandmargo wrote: > Perhaps "ONBOOT" is disabled? > > Would you send us /etc/sysconfig/network-scripts/ifcfg-eno1 ? This is what it looks like. TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=no IPV6INIT=no