Thanks for the tips, Nick.
Indeed this would be easy to correct the executable error, but I mentionned it so that Darryl can add it to his ToDo-list for the next version

Regarding the DNS, in fact I never searched for other DNS than the ones provided by my internet provider. I just heard a few years ago that Google was providing some DNS too, but you know ... the big-brother-is-watching-you syndrom
So I'll have a look to OpenDNS or other solutions (even ibVPN's DNS) but I don't really get the need to update and so on. What is needed here is to access to DNS records in order to access to internet, not to be registered to be accessed from internet. But I see that OpenDNS provides both services.

Last issue for Darryl : when I updated the servers list, the list is still incomplete : for example, Brazil and Argentina are not present in the list

Darryl Sokoloski wrote:

Michael wrote:
*edit* the module crash with MOST OF the servers, but not with some (US-dallas for example).
In all cases, when I test my online IP, it is not the one of the vpn server, so I'm not routed through the VPN.

Michael,

Can you post the log output from:
# grep ibvpn /var/log/messages

The error(s) should be obvious in there.

Hello Daryl,

Here is the log when I'm trying to connect to Paris FR 3 :

This one occurs every 5 minutes



When I start the ibVPN module :


Damn, am I stupid ?
OK, authentication problem corrected, the VPN is connected.

But second issue now : I can't access any website when the VPN is connected, it looks like a DNS or route problem ?
log :

Hello,

It seems that the module is not working. At least for me.
When i start the module, it starts, but it then stops itself after a few seconds.
Even if I check my IP address before it stops, it is still my private IP address.

This would be great to fix this little module as I subscribed to ibVPN just because of this module !

Thanks for the info regarding pip, Tony.
I'm already using Odoo, but it was a previous version and on my NAS, so the performance was not enough for me. I'll try to migrate to a new Odoo installed on my ClearOS FW, which have better performance.

Thanks Nick for the info with extra repositories, I didn't noticed that lots of repositories were easily available in this new ClearOS.

A bit of hunting shows python-werkzeug is available in clearos-centos-extras.

Yum checks rpm contents - not tarballs for dependencies. Did you do a search ?
Tarballs should only be a desperate last ditch attempt...

https://www.rpmfind.net/linux/rpm2html/search.php?query=python-werkzeug

Thanks for the answer Tony.
I thought at first that installing with pip was similar to install as a rpm, but I don't know pip.

Well, I must admit that I've not been into linux for a too long time : a basic installation of the CentOS rpm resolved this issue.
Thank you

python module not detected when installing Odoo

Hello,

I'm trying to install odoo on my CLearOS box (this is an ERP application)

So I added epel-release, postgresql and python and other things needed, and after resolving all dependencies (a lot of python modules needed), I'm facing the following issue :
one of the module required as a dependancy is python-werkzeug but this is the only one that is not available on the standard repos. Si I installed it with pip, or even from the tarball, and it installs correctly.
But when I make a yum install for odoo, this is the only python module that seems to be not detected : the installation stops with a message telling that this module is required as a dependancy.
I know that this seems to be not directly an issue related to ClearOS, but I believe that this problem needs a light system or python fix but I can't find how.

Thanks Michael for providing the hardware details - that may have solved your problem. I selected a machine as close as possible to yours (it is actually a Microsoft Home Server v 2) and stuck the install disk in and booted. Boom!!!! Just after the grey screen with the cursor in the top left-hand corner I got a panic almost identical to yours. The important difference was a few lines at the top talking about tick and clock. A search on the web revealed this hit... https://bugs.centos.org/view.php?id=9860

So I rebooted again and hit <TAB> on the options screen and added according to the report "initcall_blacklist=clocksource_done_booting" so my line at the bottom of the screen looked like
(... snipped) quiet initcall_blacklist=clocksource_done_booting

hit <ENTER> - a little anxious time then HOORAY!!! up comes the normal boot messages, no panic :-) I didn't proceed further as I'm not installing on the machine...

Give it a try Michael - make sure you use underscores between the words.

Dave - you might want to review https://bugs.centos.org/view.php?id=9860 and replace the kernel in the iso with a newer one?

EDIT: forget to add this from the bug report

Don't forget to check the installed system has the added parameter - when you upgrade to the latest kernel I don't think this is required any more

By the way, just for my personal geek culture : do you guess to what hardware the issue is linked to ?
clocksource ... this could be the MB ? or the CPU ? or the RAM ?