SSL Network Extender (SNX) not working on -current after GLIBC_233 and massive rebuild.
Hi buddies!
My name is Diniz Bortolotto. I'm a slackware64-current user. Last weekend/sunday I took the leap of faith and did a slackpkg install-new && slackpkg upgrade-all going to the new glibc 2.33 and massive rebuilt. :) Almost everything went well. I got in some moment a "GLIBC_233 not found" after 'install-new' but rebooted with a usb stick and did the usual correction for that. After that rebooted and it seemed that all was fine. In this monday, when I was going to work (home-office), I discovered that the VPN client was not working. Unfortunately there was no way to make it runs and I had to work using a Win7/VBox :eek: The message that appears when I run the 'snx' command is a not clear error "bash: /usr/bin/snx: No such file or directory". Looking/googling for that I found that the problem should be dependencies but the official list of supported distros don't includes Slackware. :( Has anyone here used SNX and could help me to identify what happended? I created a open folder in GDrive and saved in it SNX installer, binary and a png with the 'official' distros and dependencies, in case someone wants to see that. [removed] Best Regards! |
Are you trying to run a 32 bit binary on a 64 bit OS without supporting 32 bit supporting libraries?
|
Quote:
I'm running Slackware64 + multilib. Definitively there is a 32bit library problem. But, as my link to GDrive was not allowed I will try to write below more info. |
1 Attachment(s)
SNX (CheckPoint) supported Linux Platforms (uploaded a png).
In summary, on 64-bit distributions we need.
|
I have installed in my desktop ALL compat32 packages supplied by AlienBOB.
Someone have some clue on how to trace/identify the failing package/library? Like I said, before last massive upgrade/rebuilds the snx client was running well. So I suspect of something wrong with new packages rebuilt with GLIBC 2.33 |
A Slackware64 install with the proper multilib libraries should cover most, if not all of those requirements.
Usually when you see "No such file or directory" when the file does exist, it is because multilib isn't installed properly. At a minimum, to support running 32bit binaries, you need to have at least the following packages installed: Code:
aaa_glibc-solibs-2.33_multilib-x86_64-1alien.txz Code:
gcc-10.2.0_multilib-x86_64-4alien.txz Code:
ls /var/lib/pkgtools/packages/*glibc* |
Quote:
I couldn't find multilib for glibc-solibs and glibc-2.33. That's weird! I will investigate and try to figure out what happened. Below are my packages. Code:
root@darkstar:~# ls /var/lib/pkgtools/packages/*glibc* |
Quote:
Code:
root@darkstar:~# ls -1 /var/lib/pkgtools/packages/*glibc* When I got those annoying messages about GLIBC_2.33 not found, I booted and reinstalled glibc packages from my usb drive. But the original ones not the multilib. :doh: |
Almost there... and 'voila'!
Ok. That is already working now!
Again: Thanks a lot for your reply bassmadrigal! :) Sometimes we just need a friend's help to easily solve a problem. :hattip: I will explain below what I did just for reference to another buddies. :twocents: Now that I upgraded glibc and glibc-solibs to multilib version i'm getting this: Code:
root@darkstar:~# snx libstdc++.so.5 last location before rebuilds was: Code:
/var/lib/pkgtools/removed_packages/aaa_elflibs-compat32-15.0-x86_64-29compat32:usr/lib/libstdc++.so.5.0.7 Code:
Mon Feb 8 05:13:26 UTC 2021 Code:
root@darkstar:/mnt/SlackMirror# installpkg multilib-current/slackware64-compat32/a-compat32/aaa_libraries-compat32-15.0-x86_64-2compat32.txz Code:
diniz@darkstar:~$ /usr/bin/snx -s xxx.yyy.com.br -c /home/diniz/Fnnnnnn.p12 |
Glad you got it working! Sometimes a little nudge is all we need to figure it out :)
|
All times are GMT -5. The time now is 02:58 AM. |