March 2017 - openSUSE Users - openSUSE Mailing Lists

[opensuse] grub on raid
by jdd 18 Mar '17

18 Mar '17

Hello, I'm in the way of building a 42.2 server at home on a fiber line. I use a three disk raid mirror on lvm/mdadm it runs for three month without problem. still experimental, not in production. Yesterday I did a zypper up and had lot of updates. Some of them, specially grub and kernel ones didn't went well, some post install problem. "Control C" and zypper up again allowed the update to go to the end. but as could be expected, today I had to do a reboot (for other reasons) and the computer don't reboot. It stops on initial grub greetings and then error reading of first sector of disk 1, go to rescue mode (screen copy): http://dodin.org/owncloud/index.php/s/eUPZpVHG5QyPisn is this a hardware problem? I know pretty well how to test a single disk usual computer but never had to do this on raid. what may I do? thanks jdd -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 16

[opensuse] LTO 3 Drive Error
by Paul Groves 18 Mar '17

18 Mar '17

Hi, I am getting an intermittent error on my LTO 3 drive. It is a HP StorageWorks 920 internal SCSI drive. Sometimes backups work and sometimes tar will fail with this error: tar: /dev/st3: Cannot write: Input/output error tar: Error is not recoverable: exiting now I have tried 3 old tapes and one brand new tape. It has happened on all of them. I have also run two different cleaning cartridges through the drive. Also it always fails in a different place. Sometimes it runs for 5 minutes when the error comes up, other times for an hour or so. sometimes not at all and the backup works. If I look on the monitor connected to the server I see this error: 10:0:3:0 Error on write file mark Does anyone know what this means exactly or what I should do? I read online that I should try cleaning the tape heads with isopropyl alcohol. Paul -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

6 11

[opensuse] Firefox crashes on start, after last update.
by Carlos E. R. 17 Mar '17

17 Mar '17

cer@minas-tirith:~> firefox Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `gtk-primary-button-warps-slider' of type `gboolean' from rc file value "((GString*) 0x7f9dc26210a0)" of type `gboolean' Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `gtk-primary-button-warps-slider' of type `gboolean' from rc file value "((GString*) 0x7f7c85621060)" of type `gboolean' ExceptionHandler::GenerateDump cloned child 5995 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... cer@minas-tirith:~> Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `gtk-primary-button-warps-slider' of type `gboolean' from rc file value "((GString*) 0x55e00b271fa0)" of type `gboolean' Failed to open curl lib from binary, use libcurl.so instead MozillaFirefox-52.0-55.2.x86_64 using XFCE desktop and Leap 42.2 -- Cheers / Saludos, Carlos E. R. (from 42.2 x86_64 "Malachite" (Minas Tirith))

4 14

Re: [opensuse] apache2 authenticate system users and groups
by Paul Groves 17 Mar '17

17 Mar '17

On 15/03/17 23:53, David C. Rankin wrote: > On 03/15/2017 08:13 AM, Paul Groves wrote: >> A friend just emailed me this. Apparently you are supposed to use the module >> names as he has set out below. I have tried the configuration and it is >> working as expected. >> >> <IfModule authnz_external_module> >> AddExternalAuth pwauth /usr/sbin/pwauth >> SetExternalAuthMethod pwauth pipe >> </IfModule> >> >> <IfModule authz_unixgroup_module> >> AddExternalGroup unixgroup /usr/sbin/unixgroup >> SetExternalGroupMethod unixgroup environment >> </IfModule> >> >> >> And as before: >> >> AuthType Basic >> AuthName "You shall not pass! (Unless you are a system administrator)" >> AuthBasicProvider external >> AuthExternal pwauth >> <RequireAll> >> Require valid-user >> Require unix-group sudo >> </RequireAll> > Paul, > > Thanks for the follow up and providing the results of your digging. For a > bit stricter password controls on 2.2 or 2.4, I have been using Basic auth > with a hashed password file created with dbmanage2 to provide remote access > regardless of whether there is a valid unix user. It's just another simple > option that seems to work well on 2.4 as well: > > Alias /foo/ "/srv/http/htdocs/foo/" > Alias /foo "/srv/http/htdocs/foo/" > > <Directory "/srv/http/htdocs/foo"> > Options +Indexes +FollowSymLinks > IndexOptions FancyIndexing IconsAreLinks SuppressDescription > FoldersFirst NameWidth=* > AllowOverride AuthConfig Options FileInfo Limit > # mod rewrite stuff > AuthType Basic > AuthName "Case_Restricted" > AuthBasicProvider dbm > AuthDBMType DB > AuthDBMUserFile /usr/local/lib/apache2/caseaccess > Require valid-user > </Directory> > > You create the database with, e.g > > # dbmmanage2 dbname command argument > > or with actual data > > # dbmmanage2 caseaccess adduser paul > > 'paul' can now connect from anywhere... > > you will be prompted for password which is then hashed and stored in the file. > You can view check entries with > > # dbmanage2 dbname view paul > # dbmanage2 dbmane check paul > passwd: > Thanks, Might come in handy in the future. Unfortunately not possible in my case as the server is a member of active directory and the "unix groups" and "local users" are just users from AD linked by pam -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 5

[opensuse] Firefox 52 and ESR52 require pulseaudio
by Felix Miata 17 Mar '17

17 Mar '17

Such is now default buildconfig. I don't know if alsa is enabled or not in openSUSE rpm builds. https://support.mozilla.org/t5/Videos-sound-pictures-and/Fix-common-audio-a… https://bugzilla.mozilla.org/show_bug.cgi?id=1345661 (comments inhibited) Firefox users whose installations are incompatible with pulseaudio may wish to block updating from 51.x or ESR45.x. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

4 6

[opensuse] leap42.1 - how do I get the hostname displayed on the GUI login/lock screen?
by Per Jessen 17 Mar '17

17 Mar '17

$SUBJ says it all - I'm missing the hostname. When several PC are connected via a kvm switch it's handy being able to tell where you are logging in. -- Per Jessen, Zürich (4.6°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

10 42

Fw: [opensuse] code failure between different openSUSE versions
by Alec Destry 16 Mar '17

16 Mar '17

As a temporary workaround, you might want to create an opensuse 13.2 virtual machine under your opensuse 42.2 linux and run your code in that virtual machine, while you are updating it to run on opensuse 42.2. I get the impression that you are going to have to rework all of your code in order to make it run on opensuse 42.2. ----- Original Message ----- From: "Joseph Comfort" <Joseph.Comfort(a)asu.edu> To: <opensuse(a)opensuse.org> Sent: Thursday, March 16, 2017 11:07 AM Subject: [opensuse] code failure between different openSUSE versions >I few years ago, I optained a useful C++ subroutine package, and made some >extensions to it. It worked marvelously with my own application codes. It >provides an interface from fortran code to generate CERN 'root' files. > > Recently, I updated most of my computers from SuSE v13.2 to v42.2. My > application code still works just fine on v13.2, but crashes on v42.2 -- > either complaining about a missing symbol (savehandler) or just doing core > dumps. I need some suggestions and guidance. I am trying this list > because the failure came after the OS upgrade. > > The code provides an interface to the root libraries. Originally, it > could only handle a single x.root file. I added code to have it use > multiple files. The base code is a class RootTuple. When an instance is > started, its pointer is stored in an array identified by the fortran unit > number, via a call to savehandler. When switching files, the code loads > the corresponding pointer via loadhandler. > > There were/are different versions of the root library on the two OS's. If > I use the one from v13.2 on a v42.2 machine, I also have failures. But if > I usse the more recent root library version on the v13.2 system, the code > works exactly as expected. So the root version does not seem to be the > culprit. I have GNU v4.3 compilers on v13.2, and am using v4.5 on v42.2. > (A brief test from v5.3 on a v42.2 computer did not seem to change > anything.) > > Relevant code from a user application and the library package are shown > below. The user call to 'rootinit' appears to be handled fine (the file > is opened and header information is written). The failure starts with the > savehandler call. [out_unit has a value of 44.] My machines are 64-bit. > > Was there some change to C++ language, conventions, or defaults between > v13.2 and v42.2? > What other changes in the OS were there that could affect the codes? > > I will appreciate any ideas. Thank you. > > From user code: > ...... > file = 'iotest.root' > lenfil = index(file,' ') - 1 > call rootinit(file(1:lenfil),'RootTuple','recreate') > call savehandler(out_unit) > ...... > > ------------ > > From subroutine code interface.cxx: > > #include "interface.h" > #include "RootTuple.h" > > // Declare global pointer > RootTuple *eventHandler; > RootTuple* eventHandlers[100]; > > //Push the current eventHandler to the vector. > //Stores location in passed integer. > void savehandler(int& id) { > eventHandlers[id-1]=eventHandler; > } > > //Restores an eventhandler from the array. > void loadhandler(int& id) { > eventHandler = eventHandlers[id-1]; > } > > void rootinit(const char *filename, const char *treename, const char > *fileio, > int lfilename, int ltreename, int lfileio) > { > eventHandler = new RootTuple(strFtoC(filename, lfilename), > strFtoC(treename, ltreename), strFtoC(fileio, > lfileio)); > eventHandler->Initialise(); > }//rootinit > > > -- > To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org > To contact the owner, e-mail: opensuse+owner(a)opensuse.org > > -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

1 0

[opensuse] code failure between different openSUSE versions
by Joseph Comfort 16 Mar '17

16 Mar '17

I few years ago, I optained a useful C++ subroutine package, and made some extensions to it. It worked marvelously with my own application codes. It provides an interface from fortran code to generate CERN 'root' files. Recently, I updated most of my computers from SuSE v13.2 to v42.2. My application code still works just fine on v13.2, but crashes on v42.2 -- either complaining about a missing symbol (savehandler) or just doing core dumps. I need some suggestions and guidance. I am trying this list because the failure came after the OS upgrade. The code provides an interface to the root libraries. Originally, it could only handle a single x.root file. I added code to have it use multiple files. The base code is a class RootTuple. When an instance is started, its pointer is stored in an array identified by the fortran unit number, via a call to savehandler. When switching files, the code loads the corresponding pointer via loadhandler. There were/are different versions of the root library on the two OS's. If I use the one from v13.2 on a v42.2 machine, I also have failures. But if I usse the more recent root library version on the v13.2 system, the code works exactly as expected. So the root version does not seem to be the culprit. I have GNU v4.3 compilers on v13.2, and am using v4.5 on v42.2. (A brief test from v5.3 on a v42.2 computer did not seem to change anything.) Relevant code from a user application and the library package are shown below. The user call to 'rootinit' appears to be handled fine (the file is opened and header information is written). The failure starts with the savehandler call. [out_unit has a value of 44.] My machines are 64-bit. Was there some change to C++ language, conventions, or defaults between v13.2 and v42.2? What other changes in the OS were there that could affect the codes? I will appreciate any ideas. Thank you. >From user code: ...... file = 'iotest.root' lenfil = index(file,' ') - 1 call rootinit(file(1:lenfil),'RootTuple','recreate') call savehandler(out_unit) ...... ------------ >From subroutine code interface.cxx: #include "interface.h" #include "RootTuple.h" // Declare global pointer RootTuple *eventHandler; RootTuple* eventHandlers[100]; //Push the current eventHandler to the vector. //Stores location in passed integer. void savehandler(int& id) { eventHandlers[id-1]=eventHandler; } //Restores an eventhandler from the array. void loadhandler(int& id) { eventHandler = eventHandlers[id-1]; } void rootinit(const char *filename, const char *treename, const char *fileio, int lfilename, int ltreename, int lfileio) { eventHandler = new RootTuple(strFtoC(filename, lfilename), strFtoC(treename, ltreename), strFtoC(fileio, lfileio)); eventHandler->Initialise(); }//rootinit -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

2 2

[opensuse] Error when trying to update.
by Steven Hess 16 Mar '17

16 Mar '17

I've tried to update two of my Tumbleweed installs today and got the following error: File '/suse/setup/descr/appdata-screenshots.tar' not found on medium 'http://download.opensuse.org/tumbleweed/repo/oss/' Seems to be an issue with some infrastructure. A machine I updated earlier in the day did not encounter this error. I'm stuck not really feeling free to proceed to install the latest Tumbleweed release. I really like to update on the day the update release happens Steven -- ____________ Apply appropriate technology. Use what works without prejudice. Steven L Hess ARS KC6KGE DM05gd22 Owner Flex-1500 and Flex-3000 Flex-6300, FT-857D, FT-817ND 927.0875Mhz and 441.125 Repeaters Taft Ca. openSUSE Tumbleweed KDE Plasma with Packman, Leap 42.1 -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

3 4

[opensuse] Mysterious apache server crash, systemd seems clueless, and mod_python may (or may not) be the root cause.
by Roger Oberholtzer 16 Mar '17

16 Mar '17

(Current Tumbleweed, apache2-2.4.25-3.1.x86_64 - but has been happening since original install in January) Every couple of days (I have not located that part of the pattern), my apache server dies. The only pattern I see is that is it always around midnight when it happens. ● apache2.service - The Apache Webserver Loaded: loaded (/usr/lib/systemd/system/apache2.service; enabled; vendor preset: disabled) Active: failed (Result: core-dump) since Wed 2017-03-15 00:00:03 CET; 7h ago Process: 5490 ExecStop=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k graceful-stop (code=exited, status=0/SUCCESS) Process: 5477 ExecReload=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k graceful (code=exited, status=0/SUCCESS) Process: 598 ExecStart=/usr/sbin/start_apache2 -DSYSTEMD -DFOREGROUND -k start (code=dumped, signal=ABRT) Main PID: 598 (code=dumped, signal=ABRT) Status: "Total requests: 0; Current requests/sec: 0; Current traffic: 0 B/sec" CPU: 2min 58.455s Mar 14 12:59:40 sto-opq-src systemd[1]: Starting The Apache Webserver... Mar 14 12:59:40 sto-opq-src systemd[1]: Started The Apache Webserver. Mar 15 00:00:02 sto-opq-src systemd[1]: Reloading The Apache Webserver. Mar 15 00:00:02 sto-opq-src systemd[1]: Reloaded The Apache Webserver. Mar 15 00:00:03 sto-opq-src systemd[1]: apache2.service: Main process exited, code=dumped, status=6/ABRT Mar 15 00:00:03 sto-opq-src start_apache2[5490]: httpd (pid 598?) not running Mar 15 00:00:03 sto-opq-src systemd[1]: apache2.service: Unit entered failed state. Mar 15 00:00:03 sto-opq-src systemd[1]: apache2.service: Failed with result 'core-dump'. So, it looks like the server is restarting, and then 3 minutes later dumping core. I do not know why it is restarting. And having restarted, why it would die. It has never died when restarted via systemctrl (or rcapache2). Given the repeatable time, I suspected that a con job might be the cause. But /var/spool/cron has nothing at all. So perhaps systemctrl is running something? journalctl for about that time shows: Jan 14 00:00:02 sto-opq-src systemd[1]: Starting Rotate log files... Jan 14 00:00:02 sto-opq-src systemd[1]: Reloading The Apache Webserver. Jan 14 00:00:03 sto-opq-src systemd[1]: Reloaded The Apache Webserver. Jan 14 00:00:03 sto-opq-src systemd[1]: apache2.service: Main process exited, code=dumped, status=6/ABRT Jan 14 00:00:03 sto-opq-src start_apache2[5120]: httpd (pid 1730?) not running Jan 14 00:00:03 sto-opq-src systemd[1]: apache2.service: Unit entered failed state. Jan 14 00:00:03 sto-opq-src systemd[1]: apache2.service: Failed with result 'core-dump'. Jan 14 00:00:06 sto-opq-src systemd-coredump[5118]: Process 1730 (httpd-prefork) of user 0 dumped core. So, it looks like log rotation is happening when this happens. Could it be that some apache log is getting messed with so apache dies? I have not done anything with logs, so they are set however the system and various packages have set them. If I look at apache2's error_log, I see: [Wed Mar 15 00:00:03.011278 2017] [:notice] [pid 598] mod_python: Creating 8 session mutexes based on 150 max processes and 0 max threads. [Wed Mar 15 00:00:03.011318 2017] [:notice] [pid 598] mod_python: using mutex_directory /tmp Fatal Python error: PyEval_SaveThread: NULL tstate [Wed Mar 15 00:00:03.011415 2017] [core:notice] [pid 598] AH00060: seg fault or similar nasty error detected in the parent process I'm not certain that mod_python is the cause. The apache2 server provides access to a Trac site (we love Trac: https://trac.edgewall.org/) . So we are big users of mod_python. I'm not sure how to proceed. Obviously the apache2 problem should be solved. Nonetheless, I would think systemd would ensure that the server is running. I do not see that this is happening. If it were restarted again I would see the restart in the log. I do not see this. 1. How to get systemd to restart apache2 again so it is runnung? 2. Anyone else using mod_python in apache2? -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe(a)opensuse.org To contact the owner, e-mail: opensuse+owner(a)opensuse.org

5 21