Is it possible in the portal to view how many times OBS built packages of mine have been downloaded?
Thanks
Thanks
↧
Package download statistics
↧
LEAP 15.2 error after update
yast is not working after updating from 15.1
Code:
nternal error. Please report a bug report with logs.
Run save_y2logs to get complete logs.
Caller: /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
Details: Failed to load Module 'Packages' due to: Failed to load Module 'AddOnProduct' due to: cannot load such file -- y2packager/repository↧
↧
LEAP 15.1 sddm not showing users
Hi.
Hi have opensuse 15.1 with the standard login: sddm with opensuse breaze theme.
yesterday I created a new user from cntl-alt-f2 console, then returned to graphic login with cntl-alt-f7 and select "other user" or someting similar to log in whint the new user as it was not listed in the icons over the login prompt. sunce then the system does not show the users list anymore but the "user" field to type the username.
I have tried to change themes and to change something in sddm.conf but it does not work and I can't see how to change it in the documentation of sddm.
The users have all ids over 1000
This is my sddm.conf
any ideas?
thanks
Hi have opensuse 15.1 with the standard login: sddm with opensuse breaze theme.
yesterday I created a new user from cntl-alt-f2 console, then returned to graphic login with cntl-alt-f7 and select "other user" or someting similar to log in whint the new user as it was not listed in the icons over the login prompt. sunce then the system does not show the users list anymore but the "user" field to type the username.
I have tried to change themes and to change something in sddm.conf but it does not work and I can't see how to change it in the documentation of sddm.
The users have all ids over 1000
This is my sddm.conf
Code:
abraracurcix:~ # cat /etc/sddm.conf
[Autologin]
Relogin=false
User=
[General]
HaltCommand=
InputMethod=
RebootCommand=
[Theme]
Current=breeze-openSUSE
CursorTheme=breeze_cursors
EnableAvatars=true
[Users]
HideUsers=root,pruebas
MaximumUid=65000
MinimumUid=1000
RememberLastUser=false
abraracurcix:~ #any ideas?
thanks
↧
LEAP 15.2 Partitioning - /Home, Changes
I have Leap 15.0 and 15.1 installed on sdb sharing a common swap. I keep one earlier version for emergencies. Each of these include the /Home partition. In addition I have another partition for Data I keep permanently and mount under /root.
I plan to remove Leap 15.0 (both partitions i.e. root 40 GB and /Home 20 GB) and clean install 15.2. I wish to keep /Home in separate partition. Will it be possible to use the existing 15.1 /Home partition for both 15.1 and 15.2? That is I tell 15.2 at installation to use existing /Home and not format it. I use the same passwords for both versions.
PrakashC
I plan to remove Leap 15.0 (both partitions i.e. root 40 GB and /Home 20 GB) and clean install 15.2. I wish to keep /Home in separate partition. Will it be possible to use the existing 15.1 /Home partition for both 15.1 and 15.2? That is I tell 15.2 at installation to use existing /Home and not format it. I use the same passwords for both versions.
PrakashC
↧
LEAP 15.1 My notes for updating 15.1 to 15.2
I have updated about 12 machines from 15.1 to 15.2 - 6 real and 6 virtualbox machines. Here are lessons learned.
first - make sure you are up to date
sudo zypper ref ; zypper up
reboot if any library need rebooting
second - for everyone check your repo's to see if you have 15.1 or $releasever on you http lines.
if you have 15.1 replace all the 15.1 with $releasever
to see:
grep http /etc/zypp/repos.d/*
to fix
sudo sed -i 's/15.1/$releasever/g' /etc/zypp/repos.d/*.repo
If your 15.1 machine is a guest in virtualbox you need to remove the old virtualbox entries
sudo zypper rm virtualbox\*
now disable added repos like packman and adobe
to see the repo numbers
sudo zypper lr
to disable
sudo zypper mr -d # # (where # is the repo number from the list)
I got burned by packagekit running and refreshing the repos's so we need to kill packagekitd
sudo pkill packagekitd
this next section works for wifi and ethernet - it is required for wifi
sudo zypper -vvv --releasever 15.2 ref
sudo zypper -vvv --releasever 15.2 dup --download only --allow-vendor-change
when this finishes you have to get into a console
in VirtualBox guests you use right-ctl+insert+f1 (or f2 or f3) it may be slow keep trying - it may need to switch to get root to type in - I went f3 then f1 to get root.
on real computers you use crtl+alt+f1 (of f2 or f3)
at login
root
your root password
init 3 (important to kill the gui or things can go wrong - don't worry about any lines that follow this - press return/enter if garbage is on the prompt line after this)
zypper -vvv --releasever dup --allow-vendor-change
say yes to questions on license ctrl+c out and say yes
when done
if this is virtualbox guest
zypper rm virtual\*
for all
zypper mr -e # # (this is the same as you disabled above)
reboot
first - make sure you are up to date
sudo zypper ref ; zypper up
reboot if any library need rebooting
second - for everyone check your repo's to see if you have 15.1 or $releasever on you http lines.
if you have 15.1 replace all the 15.1 with $releasever
to see:
grep http /etc/zypp/repos.d/*
to fix
sudo sed -i 's/15.1/$releasever/g' /etc/zypp/repos.d/*.repo
If your 15.1 machine is a guest in virtualbox you need to remove the old virtualbox entries
sudo zypper rm virtualbox\*
now disable added repos like packman and adobe
to see the repo numbers
sudo zypper lr
to disable
sudo zypper mr -d # # (where # is the repo number from the list)
I got burned by packagekit running and refreshing the repos's so we need to kill packagekitd
sudo pkill packagekitd
this next section works for wifi and ethernet - it is required for wifi
sudo zypper -vvv --releasever 15.2 ref
sudo zypper -vvv --releasever 15.2 dup --download only --allow-vendor-change
when this finishes you have to get into a console
in VirtualBox guests you use right-ctl+insert+f1 (or f2 or f3) it may be slow keep trying - it may need to switch to get root to type in - I went f3 then f1 to get root.
on real computers you use crtl+alt+f1 (of f2 or f3)
at login
root
your root password
init 3 (important to kill the gui or things can go wrong - don't worry about any lines that follow this - press return/enter if garbage is on the prompt line after this)
zypper -vvv --releasever dup --allow-vendor-change
say yes to questions on license ctrl+c out and say yes
when done
if this is virtualbox guest
zypper rm virtual\*
for all
zypper mr -e # # (this is the same as you disabled above)
reboot
↧
↧
LEAP 15.2 CUDA 10.1 Issues, and workaround
I have two workstations, both were running Leap 15.1. I in-place upgraded the first workstation to Leap 15.2, tested that CUDA was still functional (via Blender 2.83), and used this success as justification to perform a clean install of Leap 15.2 on my primary workstation. However, CUDA did not work after a clean install. Blender could not identify any CUDA capable devices, despite all other tests succeeding.
I use Ansible to configure my workstations, so I know for certainty that the configuration was consistent.
NVIDIA-SMI output:
NVCC output:
Confirmed NVIDIA drivers were installed fine. Even played some Portal 2.
Running Blender with the --debug-cycles flag produced this output:
Saw the same results in Blender 2.82 and 2.9 nightly. Again, these same tests worked FINE on the workstation that was in-place upgraded. And it rendered fine. But not on the workstation that was clean installed.
Searching found me this discussion. Following the advice of those posters, I compiled the sample code and got the same error as them running the deviceQuery code sample:
But this is where it gets weird. If deviceQuery is ran as an elevated user ONCE, CUDA starts working correctly for non-elevated users until the next reboot.
I experimented in disabling AppArmor, ensured my user was a member of the video group (and rebooted), upgraded to Cuda 10.2. But I can't explain why running this as root makes it work for all users, or why this is occurring on a clean install but not an upgraded install.
Any thoughts on how I can debug this further? I've got the workaround, but would prefer a solution.
I use Ansible to configure my workstations, so I know for certainty that the configuration was consistent.
NVIDIA-SMI output:
Code:
+-----------------------------------------------------------------------------+| NVIDIA-SMI 440.100 Driver Version: 440.100 CUDA Version: 10.2 ||-------------------------------+----------------------+----------------------+| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC || Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. ||===============================+======================+======================|| 0 GeForce RTX 2070 Off | 00000000:01:00.0 On | N/A || 29% 29C P8 23W / 225W | 774MiB / 7974MiB | 2% Default |+-------------------------------+----------------------+----------------------+Code:
~> /usr/local/cuda/bin/nvcc --versionnvcc: NVIDIA (R) Cuda compiler driverCopyright (c) 2005-2019 NVIDIA CorporationBuilt on Fri_Feb__8_19:08:17_PST_2019Cuda compilation tools, release 10.1, V10.1.105Running Blender with the --debug-cycles flag produced this output:
Code:
I0707 00:58:13.995280 11815 blender_python.cpp:191] Debug flags initialized to:CPU flags: AVX2 : True AVX : True SSE4.1 : True SSE3 : True SSE2 : True BVH layout : BVH8 Split : FalseCUDA flags: Adaptive Compile : FalseOptiX flags: CUDA streams : 1OpenCL flags: Device type : ALL Debug : False Memory limit : 0...I0707 00:59:02.191576 11815 device_cuda.cpp:41] CUEW initialization succeededI0707 00:59:02.397126 11815 device_cuda.cpp:43] Found precompiled kernelsCUDA cuInit: Unknown errorI0707 00:59:03.931155 11815 device_opencl.cpp:48] CLEW initialization succeeded.Saw the same results in Blender 2.82 and 2.9 nightly. Again, these same tests worked FINE on the workstation that was in-place upgraded. And it rendered fine. But not on the workstation that was clean installed.
Searching found me this discussion. Following the advice of those posters, I compiled the sample code and got the same error as them running the deviceQuery code sample:
Code:
./deviceQuery Starting... CUDA Device Query (Runtime API) version (CUDART static linking)cudaGetDeviceCount returned 999-> unknown errorResult = FAILBut this is where it gets weird. If deviceQuery is ran as an elevated user ONCE, CUDA starts working correctly for non-elevated users until the next reboot.
Code:
sudo ./deviceQuery./deviceQuery Starting... CUDA Device Query (Runtime API) version (CUDART static linking)Detected 1 CUDA Capable device(s)Device 0: "GeForce RTX 2070" CUDA Driver Version / Runtime Version 10.2 / 10.1 CUDA Capability Major/Minor version number: 7.5 Total amount of global memory: 7974 MBytes (8361672704 bytes) (36) Multiprocessors, ( 64) CUDA Cores/MP: 2304 CUDA Cores GPU Max Clock rate: 1815 MHz (1.81 GHz) Memory Clock rate: 7001 Mhz Memory Bus Width: 256-bit L2 Cache Size: 4194304 bytes Maximum Texture Dimension Size (x,y,z) 1D=(131072), 2D=(131072, 65536), 3D=(16384, 16384, 16384) Maximum Layered 1D Texture Size, (num) layers 1D=(32768), 2048 layers Maximum Layered 2D Texture Size, (num) layers 2D=(32768, 32768), 2048 layers Total amount of constant memory: 65536 bytes Total amount of shared memory per block: 49152 bytes Total number of registers available per block: 65536 Warp size: 32 Maximum number of threads per multiprocessor: 1024 Maximum number of threads per block: 1024 Max dimension size of a thread block (x,y,z): (1024, 1024, 64) Max dimension size of a grid size (x,y,z): (2147483647, 65535, 65535) Maximum memory pitch: 2147483647 bytes Texture alignment: 512 bytes Concurrent copy and kernel execution: Yes with 3 copy engine(s) Run time limit on kernels: Yes Integrated GPU sharing Host Memory: No Support host page-locked memory mapping: Yes Alignment requirement for Surfaces: Yes Device has ECC support: Disabled Device supports Unified Addressing (UVA): Yes Device supports Compute Preemption: Yes Supports Cooperative Kernel Launch: Yes Supports MultiDevice Co-op Kernel Launch: Yes Device PCI Domain ID / Bus ID / location ID: 0 / 1 / 0 Compute Mode: < Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) >deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 10.2, CUDA Runtime Version = 10.1, NumDevs = 1Result = PASSI experimented in disabling AppArmor, ensured my user was a member of the video group (and rebooted), upgraded to Cuda 10.2. But I can't explain why running this as root makes it work for all users, or why this is occurring on a clean install but not an upgraded install.
Any thoughts on how I can debug this further? I've got the workaround, but would prefer a solution.
↧
LEAP 15.2 New error message
Trying to run a small program I wrote I get...
What does it mean and how do I get rid of it? In my opinion any executable that I create, running under my login on a non-networked desktop does not need to be protected.
Thanks in advance.
Code:
Invalid MIT-MAGIC-COOKIE-1 keyion@localhost:~>Thanks in advance.
↧
[security-announce] openSUSE-SU-2020:0933-1: moderate: Security update for rust, rust-cbindgen
openSUSE Security Update: Security update for rust, rust-cbindgen ______________________________________________________________________________ Announcement ID: openSUSE-SU-2020:0933-1 Rating: moderate References: #1115645 #1154817 #1173202 Cross-Referen...
More...
More...
↧
LEAP 15.2 Kmail Migration : which db manager ? Mysql ? Postgres ? Else ?
Many people on the kdepim mailing list complained about mysql and suggested to move to postgres in order to have less bugs.
Do you share this opinion ?
Why did opensuse choose mysql ?
How to configure my new 15.2 with another db manager than the default before i import the mails ?
Thanks for your answers.
Do you share this opinion ?
Why did opensuse choose mysql ?
How to configure my new 15.2 with another db manager than the default before i import the mails ?
Thanks for your answers.
↧
↧
LEAP 15.1 No graphics after uninstalling amdgpu-pro
Hi,
I have a AMD Radeon RX570 graphics card in a system currently running Leap 15.1. I use the amdgpu-pro driver for its OpenCL support. In preparation for a system upgrade to Leap 15.2, I wanted to uninstall the driver using the included uninstallation script amdgpu-pro-uninstall. But after uninstalling the driver and rebooting the system, the login screen won't show anymore. If I login on the consol xrandr lists no display at all while dmesg shows the amdgpu driver loading fine.
I can see the following errors in the logs:
I already checked whether I have the required packages installed and as far as I can see, that should be the case. Here are the related packages installed:
I also didn't change the X11 configuration (at least on purpose):
What surprises me is that this is not the first time I uninstalled amdgpu-pro. And when I did before, I had no issues using the graphics card with the default kernel driver. One thing that strikes me, though, is that I think (if I recall correctly) when uninstalling amdgpu-pro there were other packages around MESA reinstalled in order to meet dependencies. That does not happen when I uninstall the driver now. I might be mistaken in my recollection, though.
Am I missing something? What else could prevent the default amdgpu driver from being usable?
Thanks and regards,
Timo
I have a AMD Radeon RX570 graphics card in a system currently running Leap 15.1. I use the amdgpu-pro driver for its OpenCL support. In preparation for a system upgrade to Leap 15.2, I wanted to uninstall the driver using the included uninstallation script amdgpu-pro-uninstall. But after uninstalling the driver and rebooting the system, the login screen won't show anymore. If I login on the consol xrandr lists no display at all while dmesg shows the amdgpu driver loading fine.
I can see the following errors in the logs:
Code:
sddm-greeter[1907]: QXcbIntegration: Cannot create platform OpenGL context, neither GLX nor EGL are enabled
sddm-greeter[1907]: Failed to create OpenGL context for format QSurfaceFormat(version 2.0, options QFlags<QSurfaceFormat::FormatOption>(), depthBufferSize 24, redBufferSize -1, greenBufferSize -1, blueBufferSize -1, alphaBufferSize -1, stencilBufferSize 8, samples -1, swapBehavior QSurfaceFormat::SwapBehavior(DoubleBuffer), swapInterval 1, profile QSurfaceFormat::OpenGLContextProfile(NoProfile))Code:
rpm -qa --qf "%{NAME}\n" | grep -i -e amdgpu -e mesa -e drm -e 'libe?gl' -e x11 | sort | tr '\n' ' '
dbus-1-x11 ghostscript-x11 libdrm2 libdrm_amdgpu1 libdrm_intel1 libdrm_nouveau2 libdrm_radeon1 libqt4-x11 libQt5X11Extras5 libva-drm2 libva-x11-2 libvigraimpex11 libX11-6 libX11-data libX11-xcb1 libxkbcommon-x11-0 Mesa Mesa-dri Mesa-gallium Mesa-libEGL1 Mesa-libGL1 Mesa-libglapi0 Mesa-libOpenCL Mesa-libva patterns-base-x11 patterns-base-x11_enhanced patterns-base-x11_opt patterns-yast-x11_yast perl-X11-Protocol pulseaudio-module-x11 x11perf x11-tools xf86-video-amdgpu xorg-x11 xorg-x11-driver-input xorg-x11-driver-video xorg-x11-essentials xorg-x11-fonts xorg-x11-fonts-core xorg-x11-libs xorg-x11-libX11-ccache xorg-x11-server xorg-x11-server-extra xorg-x11-server-wayland xorg-x11-Xvnc xorg-x11-Xvnc-module yast2-x11HTML Code:
grep -v '^#' /etc/X11/xorg.conf.d/10-amdgpu.conf /etc/X11/xorg.conf.d/50-device.conf
/etc/X11/xorg.conf.d/10-amdgpu.conf:Section "OutputClass"
/etc/X11/xorg.conf.d/10-amdgpu.conf: Identifier "AMDgpu"
/etc/X11/xorg.conf.d/10-amdgpu.conf: MatchDriver "amdgpu"
/etc/X11/xorg.conf.d/10-amdgpu.conf: Driver "amdgpu"
/etc/X11/xorg.conf.d/10-amdgpu.conf:EndSectionWhat surprises me is that this is not the first time I uninstalled amdgpu-pro. And when I did before, I had no issues using the graphics card with the default kernel driver. One thing that strikes me, though, is that I think (if I recall correctly) when uninstalling amdgpu-pro there were other packages around MESA reinstalled in order to meet dependencies. That does not happen when I uninstall the driver now. I might be mistaken in my recollection, though.
Am I missing something? What else could prevent the default amdgpu driver from being usable?
Thanks and regards,
Timo
↧
LEAP 15.1 Network settings problem
Hello,
This afternoon I wanted to see YaST -> Network Settings, but after loading that module, YaST got back message:
Network is currently handled by NetworkManager
or completely disabled. YaST is unable to configure some options.
Some "cards"are almost totaly "grey" (disabled): Overview - complitely disablec; Hostname/DNS just field to enter hostname can be changed - rest is "grey" Routing - totaly disabled
What is wrong? Did I do something wrong? The only thing I did today is connecting one more laptop in router.
Thank you for answering my questions.
This afternoon I wanted to see YaST -> Network Settings, but after loading that module, YaST got back message:
Quote:
Network is currently handled by NetworkManager
or completely disabled. YaST is unable to configure some options.
What is wrong? Did I do something wrong? The only thing I did today is connecting one more laptop in router.
Thank you for answering my questions.
↧
[security-announce] openSUSE-SU-2020:0934-1: moderate: Security update for ntp
openSUSE Security Update: Security update for ntp ______________________________________________________________________________ Announcement ID: openSUSE-SU-2020:0934-1 Rating: moderate References: #1125401 #1169740 #1171355 #1172651 #1173334 #992038 Cro...
More...
More...
↧
Leap 15.2: После свежей установки нужно понижать версию VLC до 3.0.10 для кодеков из Packman
Leap 15.2: После свежей установки (не обновления с предыдущего выпуска) нужно понижать версию VLC до 3.0.10 для установки кодеков из 3.0.10.
По умолчанию ставится VLC 3.0.11. Кодеки в Packman собираются для 3.0.10, ибо в Leap 15.1 и 15.2 glibc 2.26, а нужна 2.29+.
Вопрос поднят, сообщения об ошибке созданы:
https://bugzilla.opensuse.org/show_bug.cgi?id=1173734
https://bugzilla.opensuse.org/show_bug.cgi?id=1173761
, обновить glibc можно.
Обновления VLC выше 3.0.10 с кодеками 3.0.10 пока что не будет. Если только руками собирать, причём не в OBS.
О кодеках: https://forums.opensuse.org/showthre...-be-installed)
Если брать из VLC: https://download.videolan.org/pub/vi...uSE/Leap_15.2/ - не пробовал ещё.
По умолчанию ставится VLC 3.0.11. Кодеки в Packman собираются для 3.0.10, ибо в Leap 15.1 и 15.2 glibc 2.26, а нужна 2.29+.
Вопрос поднят, сообщения об ошибке созданы:
https://bugzilla.opensuse.org/show_bug.cgi?id=1173734
https://bugzilla.opensuse.org/show_bug.cgi?id=1173761
, обновить glibc можно.
Обновления VLC выше 3.0.10 с кодеками 3.0.10 пока что не будет. Если только руками собирать, причём не в OBS.
О кодеках: https://forums.opensuse.org/showthre...-be-installed)
Если брать из VLC: https://download.videolan.org/pub/vi...uSE/Leap_15.2/ - не пробовал ещё.
↧
↧
LEAP 15.2 mariadb issues
Since I upgraded from 15.1 to 15.2, I can no longer access my mariadb databases from my local Drupal instances. phpMyAdmin lets me connect, and the databases are all there, as are the user accounts. But phpMyAdmin says
However, mbstring is installed for php7. phpinfo says that Multibyte String Functions are installed.
There are no entries in /var/log/mysql/*. PHP is PHP Version 7.4.6
I could use some suggestions as where to look next.
Thanks for any help.
Code:
![]()
The mbstring PHP extension was not found and you seem to be using a multibyte charset. Without the mbstring extension phpMyAdmin is unable to split strings correctly and it may result in unexpected results.
The mbstring PHP extension was not found and you seem to be using a multibyte charset. Without the mbstring extension phpMyAdmin is unable to split strings correctly and it may result in unexpected results.There are no entries in /var/log/mysql/*. PHP is PHP Version 7.4.6
I could use some suggestions as where to look next.
Thanks for any help.
↧
LEAP 15.1 update van Leap-15.1 geeft foutmelding
Om te beginnen: ik hoop dat dit de juiste plek is voor het melden van een probleem bij het updaten (met zypper) van het systeem.
Daarna met fsck de rootpartitie en de home partitie gecontroleerd: geen fouten.
Graag advies en/of commentaar.
Hans.
Code:
jopes:~ # zypper clean && zypper ref && zypper lp
All repositories have been cleaned up.
Repository 'Packman Repository' is up to date.
Repository 'Non-OSS opslagruimte' is up to date.
Repository 'Hoofd-opslagruimte' is up to date.
Repository 'Hoofd-opslagruimte voor bijwerken' is up to date.
Repository 'Opslagruimte voor bijwerken (niet-Oss)' is up to date.
All repositories have been refreshed.
Loading repository data...
Reading installed packages...
/usr/include/c++/7/bits/stl_vector.h:797: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](std::vector<_Tp, _Alloc>::size_type) [with _Tp = std::__cxx11::basic_string<char>; _Alloc = std::allocator<std::__cxx11::basic_string<char> >; std::vector<_Tp, _Alloc>::reference = std::__cxx11::basic_string<char>&; std::vector<_Tp, _Alloc>::size_type = long unsigned int]: Assertion '__builtin_expect(__n < this->size(), true)' failed.
Aborted (core dumped)
jopes:~ #Graag advies en/of commentaar.
Hans.
↧
TUMBLEWEED AND LEAP Community repositories missing
Hello guys,
I've noticed that the community repositories for Nvidia drivers, packman and libdvdcss are not available anymore for Tumbleweed and for Leap.
Has the way changed to add them or were they intentionally removed?
Thanks in advance!
Have a nice day!
I've noticed that the community repositories for Nvidia drivers, packman and libdvdcss are not available anymore for Tumbleweed and for Leap.
Has the way changed to add them or were they intentionally removed?
Thanks in advance!
Have a nice day!
↧
LEAP 15.2 Why Is Netbeans Not In The Repositories?
Hi folks. I just tried to install Netbeans through YaST And found that a few components of Netbeans are in the repositories, but the actual IDE itself is not. The Apache foundation took stewardship of Netbeans a while ago, didn't it? Has some licensing change during the transition to the Apache foundation meant that Netbeans can't be included in the repositories? Henk said that I should just wait for the Packman and Nvidia repositories to be added to 15.2 so that I can install the video codecs and my GPU driver. Is it likely that Netbeans will be in the Packman repositories for similar reasons that the video codecs are, or should I be looking to download, install and keep it up-to-date manually?
↧
↧
LEAP 15.2 Hawk backend fails to start
Hello All;
Installed openSUSE Leap 15.2, then KVM tools, Hawk and cluster modules.
I can ha-cluster-init, and indeed it does config the cluster
It also states that I can use HAWK2 (HA Web Konsole). But when I to to https://192.168.12.242:7630/ I'm greeted with a blank white screen
the hawk deamon is running
systemctl status hawk
● hawk.service - HA Web Konsole
Loaded: loaded (/usr/lib/systemd/system/hawk.service; enabled; vendor preset>
Active: active (running) since Mon 2020-07-06 21:43:25 MDT; 17min ago
Main PID: 1903 (hawk-apiserver)
But not the hawk-backend
systemctl status hawk-backend
● hawk-backend.service - HA Web Konsole Backend
Loaded: loaded (/usr/lib/systemd/system/hawk-backend.service; static; vendor>
Active: failed (Result: exit-code) since Mon 2020-07-06 22:01:52 MDT; 5s ago
Process: 14663 ExecStart=/usr/bin/puma.ruby2.5 -C /usr/share/hawk/config/puma>
Main PID: 14663 (code=exited, status=1/FAILURE)
So, looking at the /var/log/messages file, this is what I get
---
2020-07-06T21:52:07.277099-06:00 nss-leap152 systemd[1]: Started HA Web Konsole Backend.
2020-07-06T21:52:07.393681-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] Puma starting in cluster mode...
2020-07-06T21:52:07.393886-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] * Version 3.11.0 (ruby 2.5.8-p224), codename: Love Song
2020-07-06T21:52:07.393999-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] * Min threads: 0, max threads: 1
2020-07-06T21:52:07.394113-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] * Environment: production
2020-07-06T21:52:07.394231-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] * Process workers: 1
2020-07-06T21:52:07.394350-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] * Preloading application
2020-07-06T21:52:07.710011-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] ! Unable to load application: Gem::ConflictError: Unable to activate sass-rails-5.1.0, because railties-5.1.4 conflicts with railties (>= 5.2.0)
2020-07-06T21:52:07.710267-06:00 nss-leap152 puma.ruby2.5[10033]: /usr/lib64/ruby/2.5.0/rubygems/specification.rb:2327:in `raise_if_conflicts': Unable to activate sass-rails-5.1.0, because railties-5.1.4 conflicts with railties (>= 5.2.0) (Gem::ConflictError)
2020-07-06T21:52:07.710480-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/specification.rb:1438:in `activate'
2020-07-06T21:52:07.710599-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:68:in `block in gem'
2020-07-06T21:52:07.710749-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:67:in `synchronize'
2020-07-06T21:52:07.710878-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:67:in `gem'
2020-07-06T21:52:07.710991-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/share/hawk/config/boot.rb:35:in `<top (required)>'
2020-07-06T21:52:07.711074-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
2020-07-06T21:52:07.711158-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
2020-07-06T21:52:07.711239-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/share/hawk/config/application.rb:4:in `<top (required)>'
2020-07-06T21:52:07.711320-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/share/hawk/config/environment.rb:5:in `require_relative'
2020-07-06T21:52:07.711400-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/share/hawk/config/environment.rb:5:in `<top (required)>'
2020-07-06T21:52:07.711477-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
2020-07-06T21:52:07.711573-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
2020-07-06T21:52:07.711650-06:00 nss-leap152 puma.ruby2.5[10033]: #011from config.ru:4:in `block in <main>'
2020-07-06T21:52:07.711726-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.8/lib/rack/builder.rb:55:in `instance_eval'
2020-07-06T21:52:07.711804-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.8/lib/rack/builder.rb:55:in `initialize'
2020-07-06T21:52:07.711880-06:00 nss-leap152 puma.ruby2.5[10033]: #011from config.ru:in `new'
2020-07-06T21:52:07.711957-06:00 nss-leap152 puma.ruby2.5[10033]: #011from config.ru:in `<main>'
2020-07-06T21:52:07.712037-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.8/lib/rack/builder.rb:49:in `eval'
2020-07-06T21:52:07.712114-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.8/lib/rack/builder.rb:49:in `new_from_string'
2020-07-06T21:52:07.712186-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.8/lib/rack/builder.rb:40:in `parse_file'
2020-07-06T21:52:07.712257-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/configuration.rb:318:in `load_rackup'
2020-07-06T21:52:07.712327-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/configuration.rb:243:in `app'
2020-07-06T21:52:07.712401-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/runner.rb:138:in `load_and_bind'
2020-07-06T21:52:07.712472-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/cluster.rb:397:in `run'
2020-07-06T21:52:07.712540-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/launcher.rb:183:in `run'
2020-07-06T21:52:07.712611-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/cli.rb:77:in `run'
2020-07-06T21:52:07.712680-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/bin/puma:10:in `<top (required)>'
2020-07-06T21:52:07.712772-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/bin/puma.ruby2.5:23:in `load'
2020-07-06T21:52:07.712848-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/bin/puma.ruby2.5:23:in `<main>'
2020-07-06T21:52:07.713821-06:00 nss-leap152 systemd[1]: hawk-backend.service: Main process exited, code=exited, status=1/FAILURE
2020-07-06T21:52:07.714104-06:00 nss-leap152 systemd[1]: hawk-backend.service: Unit entered failed state.
2020-07-06T21:52:07.714242-06:00 nss-leap152 systemd[1]: hawk-backend.service: Failed with result 'exit-code'.
---
query the rpm
nss-leap152:~ # rpm -qa | grep railties
ruby2.5-rubygem-railties-5_1-5.1.4-lp152.3.3.x86_64
ruby2.5-rubygem-railties-5.2-5.2.3-lp152.2.3.x86_64
nss-leap152:~ # rpm -qa | grep sass
ruby2.5-rubygem-sass-3.5.3-lp152.3.3.x86_64
ruby2.5-rubygem-sass-rails-5.1-5.1.0-lp152.1.1.x86_64
ruby2.5-rubygem-sass-listen-4.0.0-lp152.3.3.x86_64
Any suggestions, comments, guesses?
Installed openSUSE Leap 15.2, then KVM tools, Hawk and cluster modules.
I can ha-cluster-init, and indeed it does config the cluster
It also states that I can use HAWK2 (HA Web Konsole). But when I to to https://192.168.12.242:7630/ I'm greeted with a blank white screen
the hawk deamon is running
systemctl status hawk
● hawk.service - HA Web Konsole
Loaded: loaded (/usr/lib/systemd/system/hawk.service; enabled; vendor preset>
Active: active (running) since Mon 2020-07-06 21:43:25 MDT; 17min ago
Main PID: 1903 (hawk-apiserver)
But not the hawk-backend
systemctl status hawk-backend
● hawk-backend.service - HA Web Konsole Backend
Loaded: loaded (/usr/lib/systemd/system/hawk-backend.service; static; vendor>
Active: failed (Result: exit-code) since Mon 2020-07-06 22:01:52 MDT; 5s ago
Process: 14663 ExecStart=/usr/bin/puma.ruby2.5 -C /usr/share/hawk/config/puma>
Main PID: 14663 (code=exited, status=1/FAILURE)
So, looking at the /var/log/messages file, this is what I get
---
2020-07-06T21:52:07.277099-06:00 nss-leap152 systemd[1]: Started HA Web Konsole Backend.
2020-07-06T21:52:07.393681-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] Puma starting in cluster mode...
2020-07-06T21:52:07.393886-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] * Version 3.11.0 (ruby 2.5.8-p224), codename: Love Song
2020-07-06T21:52:07.393999-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] * Min threads: 0, max threads: 1
2020-07-06T21:52:07.394113-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] * Environment: production
2020-07-06T21:52:07.394231-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] * Process workers: 1
2020-07-06T21:52:07.394350-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] * Preloading application
2020-07-06T21:52:07.710011-06:00 nss-leap152 puma.ruby2.5[10033]: [10033] ! Unable to load application: Gem::ConflictError: Unable to activate sass-rails-5.1.0, because railties-5.1.4 conflicts with railties (>= 5.2.0)
2020-07-06T21:52:07.710267-06:00 nss-leap152 puma.ruby2.5[10033]: /usr/lib64/ruby/2.5.0/rubygems/specification.rb:2327:in `raise_if_conflicts': Unable to activate sass-rails-5.1.0, because railties-5.1.4 conflicts with railties (>= 5.2.0) (Gem::ConflictError)
2020-07-06T21:52:07.710480-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/specification.rb:1438:in `activate'
2020-07-06T21:52:07.710599-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:68:in `block in gem'
2020-07-06T21:52:07.710749-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:67:in `synchronize'
2020-07-06T21:52:07.710878-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_gem.rb:67:in `gem'
2020-07-06T21:52:07.710991-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/share/hawk/config/boot.rb:35:in `<top (required)>'
2020-07-06T21:52:07.711074-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
2020-07-06T21:52:07.711158-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
2020-07-06T21:52:07.711239-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/share/hawk/config/application.rb:4:in `<top (required)>'
2020-07-06T21:52:07.711320-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/share/hawk/config/environment.rb:5:in `require_relative'
2020-07-06T21:52:07.711400-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/share/hawk/config/environment.rb:5:in `<top (required)>'
2020-07-06T21:52:07.711477-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
2020-07-06T21:52:07.711573-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/2.5.0/rubygems/core_ext/kernel_require.rb:59:in `require'
2020-07-06T21:52:07.711650-06:00 nss-leap152 puma.ruby2.5[10033]: #011from config.ru:4:in `block in <main>'
2020-07-06T21:52:07.711726-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.8/lib/rack/builder.rb:55:in `instance_eval'
2020-07-06T21:52:07.711804-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.8/lib/rack/builder.rb:55:in `initialize'
2020-07-06T21:52:07.711880-06:00 nss-leap152 puma.ruby2.5[10033]: #011from config.ru:in `new'
2020-07-06T21:52:07.711957-06:00 nss-leap152 puma.ruby2.5[10033]: #011from config.ru:in `<main>'
2020-07-06T21:52:07.712037-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.8/lib/rack/builder.rb:49:in `eval'
2020-07-06T21:52:07.712114-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.8/lib/rack/builder.rb:49:in `new_from_string'
2020-07-06T21:52:07.712186-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/rack-2.0.8/lib/rack/builder.rb:40:in `parse_file'
2020-07-06T21:52:07.712257-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/configuration.rb:318:in `load_rackup'
2020-07-06T21:52:07.712327-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/configuration.rb:243:in `app'
2020-07-06T21:52:07.712401-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/runner.rb:138:in `load_and_bind'
2020-07-06T21:52:07.712472-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/cluster.rb:397:in `run'
2020-07-06T21:52:07.712540-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/launcher.rb:183:in `run'
2020-07-06T21:52:07.712611-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/lib/puma/cli.rb:77:in `run'
2020-07-06T21:52:07.712680-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/lib64/ruby/gems/2.5.0/gems/puma-3.11.0/bin/puma:10:in `<top (required)>'
2020-07-06T21:52:07.712772-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/bin/puma.ruby2.5:23:in `load'
2020-07-06T21:52:07.712848-06:00 nss-leap152 puma.ruby2.5[10033]: #011from /usr/bin/puma.ruby2.5:23:in `<main>'
2020-07-06T21:52:07.713821-06:00 nss-leap152 systemd[1]: hawk-backend.service: Main process exited, code=exited, status=1/FAILURE
2020-07-06T21:52:07.714104-06:00 nss-leap152 systemd[1]: hawk-backend.service: Unit entered failed state.
2020-07-06T21:52:07.714242-06:00 nss-leap152 systemd[1]: hawk-backend.service: Failed with result 'exit-code'.
---
query the rpm
nss-leap152:~ # rpm -qa | grep railties
ruby2.5-rubygem-railties-5_1-5.1.4-lp152.3.3.x86_64
ruby2.5-rubygem-railties-5.2-5.2.3-lp152.2.3.x86_64
nss-leap152:~ # rpm -qa | grep sass
ruby2.5-rubygem-sass-3.5.3-lp152.3.3.x86_64
ruby2.5-rubygem-sass-rails-5.1-5.1.0-lp152.1.1.x86_64
ruby2.5-rubygem-sass-listen-4.0.0-lp152.3.3.x86_64
Any suggestions, comments, guesses?
↧
[security-announce] openSUSE-SU-2020:0940-1: important: Security update for python3
openSUSE Security Update: Security update for python3 ______________________________________________________________________________ Announcement ID: openSUSE-SU-2020:0940-1 Rating: important References: #1173274 Cross-References: CVE-2020-14422 Affected ...
More...
More...
↧
[security-announce] openSUSE-SU-2020:0939-1: important: Security update for chocolate-doom
openSUSE Security Update: Security update for chocolate-doom ______________________________________________________________________________ Announcement ID: openSUSE-SU-2020:0939-1 Rating: important References: #1173595 Cross-References: CVE-2020-14983 Af...
More...
More...
↧