Bug 11699 - MageiaUpdate refuses to run 4 of 5 times when home is a NFS-share: "Cannot be run in console mode."
Summary: MageiaUpdate refuses to run 4 of 5 times when home is a NFS-share: "Cannot be...
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: x86_64 Linux
Priority: Low minor
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-18 19:52 CET by Hartmut Goebel
Modified: 2015-03-31 16:05 CEST (History)
2 users (show)

See Also:
Source RPM: rpmdrake-5.49-1.mga3.src.rpm
CVE:
Status comment:


Attachments

Description Hartmut Goebel 2013-11-18 19:52:50 CET
Description of problem:

MageiaUpdate refuses to run 4 of 5 times, when the home-directory is a NFS-share: "Cannot be run in console mode.", but I'm running in X11-mode.

When trying to run MageiaUpdate again and again, it successfully starts after approx. 3 or 5 tries. This effect only occurs if the users home is on a NFS-share.

Version-Release number of selected component (if applicable): 5.49-1.mga3

How reproducible: absolutely

Steps to Reproduce:
1. Create a user having his hoe on a NFSv4 share.
2. Login in graphics mode (KDE) as this user.
3. Open a Konsole
4. call "MageiaUpdate"
5. try several times

I tested this with a user having his home on the local disk: MageiaUpdate runs fine.
But as soon as the users home is moved to a NFSv4 share, this problem occurs.

Reproducible: 

Steps to Reproduce:
Comment 1 Hartmut Goebel 2013-11-18 19:53:28 CET
Please let me know what I can do to help tracking this down.
Comment 2 Hartmut Goebel 2013-11-18 19:55:19 CET
I forgot to mention a nasty side-effect: MageiaUpdate is run from mgaapplet. (This is how I found this problem.) So users are confused why they are unable to update the software.
David Walser 2013-11-22 19:02:26 CET

CC: (none) => thierry.vignaud

Comment 3 Robert Courtright 2013-12-20 17:18:24 CET
It's not just home but anything! It affect's autofs and a hard mounts.
In my case it wont mount at all.
My server is also a Mageia4 Beta 2 with 2 nics a firewall and file server.
It works as expected. Could it be that the firewall is not allowing the nfs thru on a singe nic system? Even when turn off.

CC: (none) => rbcourt

Comment 4 Hartmut Goebel 2013-12-20 18:04:41 CET
(In reply to Robert  Courtright from comment #3)
> It's not just home but anything! It affect's autofs and a hard mounts.
> In my case it wont mount at all.

I wonder, how is your comment related to this bug? Thus bug is about a problem MageiaUpdate has. This bug is *not* about a mount problem.
Comment 5 Robert Courtright 2013-12-20 22:11:37 CET
They both are releated to NFS now working as it should. 

You have problem when your home is mounted as an NFS share. When not using NFS MageiaUpdate works without problem.

Mine is all NFS shares.
Comment 6 Hartmut Goebel 2014-02-17 09:51:24 CET
On my system, NFS is working as expected. There must be another reason.
Comment 7 Hartmut Goebel 2014-02-17 09:53:19 CET
I just filed bug #12799, which is about to the current working directory being on a nfs-share with root-sqash. I thought, this might be the course for this one, but this one works somewhen.
Thierry Vignaud 2014-06-27 16:05:44 CEST

Priority: Normal => Low

Comment 8 Marja Van Waes 2015-03-31 16:05:42 CEST
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.