[opensuse-factory] leap 15 beta error while connecting to a nfs share with yast2
* Karl Sinn
Hi,
attached the y2logs.
please consider using a service such as https://paste.opensuse.org rather than sending large files to *everyone* on the list. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On 2018-02-25 14:28, Karl Sinn wrote:
Hi,
attached the y2logs.
I think that here you should better describe the problem, only send the logs if asked. Normally the logs are attached to an official bug report, in Bugzilla, not in the mail list. And even then you have to describe the problem. What should we search for in that megabyte of compressed logs? -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
Am 25.02.2018 um 15:21 schrieb Carlos E. R.:
Hi,
attached the y2logs. I think that here you should better describe the problem, only send the logs if asked. Normally the logs are attached to an official bug report, in Bugzilla, not in the mail list. And even then you have to describe
On 2018-02-25 14:28, Karl Sinn wrote: the problem. What should we search for in that megabyte of compressed logs?
I thought the problem would be clear in the subject: when I use the yast2 moduls for nfs clients the error message pops up when I click on he button to search for nfs servers. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Karl Sinn
Am 25.02.2018 um 15:21 schrieb Carlos E. R.:
Hi,
attached the y2logs. I think that here you should better describe the problem, only send the logs if asked. Normally the logs are attached to an official bug report, in Bugzilla, not in the mail list. And even then you have to describe
On 2018-02-25 14:28, Karl Sinn wrote: the problem. What should we search for in that megabyte of compressed logs?
I thought the problem would be clear in the subject: when I use the yast2 moduls for nfs clients the error message pops up when I click on he button to search for nfs servers.
have the nfs servers been set up correctly? are you able to connect to the nfs servers from other boxes. what differs in the set up on the other boxes? is the nfs server running? nfsd on the nfs server, what says "cat /etc/exports"? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
have the nfs servers been set up correctly? are you able to connect to the nfs servers from other boxes. what differs in the set up on the other boxes? is the nfs server running? nfsd on the nfs server, what says "cat /etc/exports"?
Hi, yast2 has a bug, some term is used that's unknown during runtime (should be more detailed in the logfiles). I understood this is not the right place to post this but my experiences with the bug trackers are not good. My bugreports usually stay untouched forever. That's why I posted the message here. If this somehow get's to the developers so they can solve this, would be great. If not, also good. FYI: the system is already replaced by another openSUSE release. Karl -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
* Karl Sinn
have the nfs servers been set up correctly? are you able to connect to the nfs servers from other boxes. what differs in the set up on the other boxes? is the nfs server running? nfsd on the nfs server, what says "cat /etc/exports"?
Hi,
yast2 has a bug, some term is used that's unknown during runtime (should be more detailed in the logfiles).
I understood this is not the right place to post this but my experiences with the bug trackers are not good. My bugreports usually stay untouched forever. That's why I posted the message here. If this somehow get's to the developers so they can solve this, would be great. If not, also good.
FYI: the system is already replaced by another openSUSE release.
so any further action is fruitless w/o someone to consult about errors, error messages, and retrial. and you didn't file a bug report so this conversation was a waste. please post again when you are more insterested in a result and/or a solution to an identified problem. thank you, -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Registered Linux User #207535 @ http://linuxcounter.net Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
Op zondag 25 februari 2018 16:17:24 CET schreef Karl Sinn:
Am 25.02.2018 um 15:21 schrieb Carlos E. R.:
On 2018-02-25 14:28, Karl Sinn wrote:
Hi,
attached the y2logs.
I think that here you should better describe the problem, only send the logs if asked. Normally the logs are attached to an official bug report, in Bugzilla, not in the mail list. And even then you have to describe the problem. What should we search for in that megabyte of compressed logs?
I thought the problem would be clear in the subject: when I use the yast2 moduls for nfs clients the error message pops up when I click on he button to search for nfs servers.
Karl, I had a look at the content of the attachment. It is containing 35 directories and subdirectories 148189 lines of tekst and 167 results for 'grep -i nfs' from those files. We're all just volunteers, with jobs, families and so on, this will take hours to plough through. We need exact error messages. "The error" means nothing, the exact one might at least give a hint on what to look for. -- Gertjan Lettink, a.k.a. Knurpht openSUSE Board Member openSUSE Forums Team Linux user #548252 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Sunday, 25 February 2018 17:18:19 CET Knurpht - Gertjan Lettink wrote:
Op zondag 25 februari 2018 16:17:24 CET schreef Karl Sinn:
Am 25.02.2018 um 15:21 schrieb Carlos E. R.:
On 2018-02-25 14:28, Karl Sinn wrote:
Hi,
attached the y2logs.
I think that here you should better describe the problem, only send the logs if asked. Normally the logs are attached to an official bug report, in Bugzilla, not in the mail list. And even then you have to describe the problem. What should we search for in that megabyte of compressed logs?
I thought the problem would be clear in the subject: when I use the yast2 moduls for nfs clients the error message pops up when I click on he button to search for nfs servers.
Karl, I had a look at the content of the attachment. It is containing 35 directories and subdirectories 148189 lines of tekst and 167 results for 'grep -i nfs' from those files. We're all just volunteers, with jobs, families and so on, this will take hours to plough through. We need exact error messages. "The error" means nothing, the exact one might at least give a hint on what to look for.
The relevant part is in YaST2/y2log at the end of the file: ``` 2018-02-25 14:18:27 <3> linux-u8rg(3512) [Ruby] yast/wfm.rb:253 Client /usr/ share/YaST2/clients/nfs.rb failed with 'undefined local variable or method `firewalld' for #Yast::NfsClient:0x0000000000f3d338' (NameError). Backtrace: /usr/share/YaST2/include/nfs/ui.rb:327:in `block in GetFstabEntry' /usr/share/YaST2/include/nfs/ui.rb:313:in `loop' /usr/share/YaST2/include/nfs/ui.rb:313:in `GetFstabEntry' /usr/share/YaST2/include/nfs/ui.rb:593:in `HandleEvent' /usr/share/YaST2/include/nfs/ui.rb:705:in `block in FstabDialog' /usr/share/YaST2/include/nfs/ui.rb:695:in `loop' /usr/share/YaST2/include/nfs/ui.rb:695:in `FstabDialog' /usr/share/YaST2/include/nfs/wizards.rb:22:in `MainSequence' /usr/share/YaST2/include/nfs/wizards.rb:30:in `block in NfsSequence' ... ``` I suggest to report a bug about this then with this information.. Regards, Oliver -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
The relevant part is in YaST2/y2log at the end of the file:
``` 2018-02-25 14:18:27 <3> linux-u8rg(3512) [Ruby] yast/wfm.rb:253 Client /usr/ share/YaST2/clients/nfs.rb failed with 'undefined local variable or method `firewalld' for #Yast::NfsClient:0x0000000000f3d338' (NameError). Backtrace: /usr/share/YaST2/include/nfs/ui.rb:327:in `block in GetFstabEntry' /usr/share/YaST2/include/nfs/ui.rb:313:in `loop' /usr/share/YaST2/include/nfs/ui.rb:313:in `GetFstabEntry' /usr/share/YaST2/include/nfs/ui.rb:593:in `HandleEvent' /usr/share/YaST2/include/nfs/ui.rb:705:in `block in FstabDialog' /usr/share/YaST2/include/nfs/ui.rb:695:in `loop' /usr/share/YaST2/include/nfs/ui.rb:695:in `FstabDialog' /usr/share/YaST2/include/nfs/wizards.rb:22:in `MainSequence' /usr/share/YaST2/include/nfs/wizards.rb:30:in `block in NfsSequence' ... ```
I suggest to report a bug about this then with this information..
puh, I went to bugzilla.opensuse.org, I logged in. first question "Product:". There's no 15 beta. No leap, no factory. No clue what to put there. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
On Monday, 26 February 2018 23:00:36 CET Karl Sinn wrote:
The relevant part is in YaST2/y2log at the end of the file:
``` 2018-02-25 14:18:27 <3> linux-u8rg(3512) [Ruby] yast/wfm.rb:253 Client /usr/ share/YaST2/clients/nfs.rb failed with 'undefined local variable or method `firewalld' for #Yast::NfsClient:0x0000000000f3d338' (NameError). Backtrace: /usr/share/YaST2/include/nfs/ui.rb:327:in `block in GetFstabEntry' /usr/share/YaST2/include/nfs/ui.rb:313:in `loop' /usr/share/YaST2/include/nfs/ui.rb:313:in `GetFstabEntry' /usr/share/YaST2/include/nfs/ui.rb:593:in `HandleEvent' /usr/share/YaST2/include/nfs/ui.rb:705:in `block in FstabDialog' /usr/share/YaST2/include/nfs/ui.rb:695:in `loop' /usr/share/YaST2/include/nfs/ui.rb:695:in `FstabDialog' /usr/share/YaST2/include/nfs/wizards.rb:22:in `MainSequence' /usr/share/YaST2/include/nfs/wizards.rb:30:in `block in NfsSequence' ... ```
I suggest to report a bug about this then with this information..
puh, I went to bugzilla.opensuse.org, I logged in. first question "Product:". There's no 15 beta. No leap, no factory. No clue what to put there.
The product is called "openSUSE Distribution". You can use this direct link https://bugzilla.opensuse.org/enter_bug.cgi?product=openSUSE Distribution&version=Leap 15.0&component=Installation Thank you for your effort, Oliver -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
https://bugzilla.opensuse.org/show_bug.cgi?id=1082919 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Monday, 2018-02-26 at 23:00 +0100, Karl Sinn wrote:
I suggest to report a bug about this then with this information..
puh, I went to bugzilla.opensuse.org, I logged in. first question "Product:". There's no 15 beta. No leap, no factory. No clue what to put there.
You have information and direct links here: https://en.opensuse.org/openSUSE:Submitting_bug_reports - -- Cheers, Carlos E. R. (from openSUSE 42.3 x86_64 "Malachite" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlqVYB8ACgkQtTMYHG2NR9XcdACfZCV9TTQlW8f5mpga3XxnTlnd +T8AoIWElkLRSIZOjlXMyCmGCjNjlIPW =dnoA -----END PGP SIGNATURE-----
On 2018-02-25 16:17, Karl Sinn wrote:
Am 25.02.2018 um 15:21 schrieb Carlos E. R.:
Hi,
attached the y2logs. I think that here you should better describe the problem, only send the logs if asked. Normally the logs are attached to an official bug report, in Bugzilla, not in the mail list. And even then you have to describe
On 2018-02-25 14:28, Karl Sinn wrote: the problem. What should we search for in that megabyte of compressed logs?
I thought the problem would be clear in the subject: when I use the yast2 moduls for nfs clients the error message pops up when I click on he button to search for nfs servers.
Not at all: you don't even say what the message says... And the subject doesn't say that a message pops up; you said that now. -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" at Telcontar)
participants (5)
-
Carlos E. R. -
Karl Sinn -
Knurpht - Gertjan Lettink -
Oliver Kurz -
Patrick Shanahan