Web-App doesn't start after updating to 2018-R1.1

  1. ‹ Older
  2. 3 months ago

    Alexandre C

    Jun 17 Pre-Release Testers, Xojo Pro Brazil

    After a new ticket on my provider, the answer…

    Have you considered the possibility of kernel-related differences? Our VPS platform runs on specially-modified 2.6 Linux kernel, which cannot be changed at the VPS level. Your VM installs likely used what CentOS ships with natively, which is a 3.x kernel. It's quite possible that the difference in kernel may be to blame here. Have you tried running your updated software on a CentOS install utilizing a 2.6 Linux kernel?

    So i'll install the 2.6 linux kernel and check if it works or not.

  3. Alexandre C

    Jun 17 Pre-Release Testers, Xojo Pro Brazil

    My VMWare CentOS 7.5 Cpanel Kernel: 3.10.0-862.3.3.el7.x86_64

    My Host Centos 7.2 Cpanel Kernel: 2.6.32-042stab128.2

    i'm trying to install older kernel on my vmware, but not success yet.

  4. René L

    Jun 17 Pre-Release Testers, Xojo Pro Ratingen, Duesseldorf, Germany

    Hello @Alexandre C,

    Looks like your Hosting Provider is using Virtuozzo System (or the "Free" Version: OpenVZ as VM Host-System. That Kernel 2.6. is a special Kernel used only by Virtuozzo and OpenVZ (and even the only in the RHEL 6.x Version).

    Best Regards,

    R. Landscheidt

  5. Alexandre C

    Jun 19 Pre-Release Testers, Xojo Pro Brazil

    Yes, the Virtualization environment is OpenVZ.

    I confirmed.

    So, compiled CGi, 64-bit for Centos 7, with virtualization environment OpenVZ, with Xojo 2018r1.1 DOES NOT WORK.

    On documentation only says "CentOS 7" is compatible…

  6. Daniel W

    Jun 19 Australia
    Edited 3 months ago

    I'm running 2018r1.1 on centos7 containers with no problems. I just had to run the following to solve dependencies.

    yum -y install libsoup libunwind.x86_64

    libunwind.x86_64 was the tricky package name for 2018r1.X

    Edit:
    I see the OP says you have already installed libunwind.x86_64 so this might not help you.

  7. Alexandre C

    Jun 21 Pre-Release Testers, Xojo Pro Brazil

    @Daniel W I'm running 2018r1.1 on centos7 containers with no problems. I just had to run the following to solve dependencies.

    yum -y install libsoup libunwind.x86_64

    libunwind.x86_64 was the tricky package name for 2018r1.X

    Edit:
    I see the OP says you have already installed libunwind.x86_64 so this might not help you.

    Yes, it's all required libraries installed, and it does not work!

    It's an incompatibility problem with OpenVZ, and i think it's because of "old" kernel version.

    Xojo inc. does not say anything about kernel versions, or cpanel, or openVZ incompatibilities.

    … so… i'm f###ed…

    I have this app about 10 years, hosted at various providers, with no problem.
    after many years finding the best cost provider, with best server processor, memory, etc… now i do not know what i'll do, because this new compiled version on 2018r1.1 does not work.

    and no one at xojo.inc are concerned to try to really go deep and find out how to fix this (not only for me, of course, but for everyone i'm sure will have this problem on near future).

  8. Alberto D

    Jun 21 Pre-Release Testers, Xojo Pro

    Sorry Alexandre that this is happening to you.

    I see that new Xojo version need newer OS all the time. I see people working with older Xojo versions to support older OS. Do you really need Xojo 2018 for your app? Maybe you can use Xojo 2017 for some time, maybe OpenVZ will upgrade in the future.

  9. Tim S

    Jun 21 Pre-Release Testers, Xojo Pro Phoenix Arizona USA

    FYI, I *still* have the same problem. Web app compiled in 2018R1, or 2018R1.1 do NOT work! 2017R3 - no problem!
    What gives????
    Tim

  10. Alexandre C

    Jun 22 Pre-Release Testers, Xojo Pro Brazil

    @Alberto D;Poo Sorry Alexandre that this is happening to you.

    I see that new Xojo version need newer OS all the time. I see people working with older Xojo versions to support older OS. Do you really need Xojo 2018 for your app? Maybe you can use Xojo 2017 for some time, maybe OpenVZ will upgrade in the future.

    Well… if i can use a newer version, to get better results, functionalities, etc, etc… WHY i'll use the older version?…

    I'm really upset with xojo.inc, because they are doing "nothing" to fix this.

    On documentation does not say anywhere the "minimum kernel version" or any other incompatibility information.

    And… believe or not, they "CLOSED" my case on FEEDBACK…

  11. Alexandre C

    Jun 22 Pre-Release Testers, Xojo Pro Brazil

    @Tim S FYI, I *still* have the same problem. Web app compiled in 2018R1, or 2018R1.1 do NOT work! 2017R3 - no problem!
    What gives????
    Tim

    I need more people to email Jason Parsley <jason@xojo.com> asking him about a fix for this…

    Do you know other people with the same problem?

    Alex

  12. Alberto D

    Jun 22 Pre-Release Testers, Xojo Pro

    Sorry Alexandre, English is not my first language and maybe I can't translate my ideas into words.

    I think Tim's problem is with Raspberry and is not related with this problem (that's what Jason and Greg said).

    I understand that you are angry, but I don't see how you expect Xojo to help you. Your host provider said: Our VPS platform runs on specially-modified 2.6 Linux kernel, do you really think that when Xojo put the requirement to run the software do they mean that any 'specially-modified' installations should also work? Will you be less angry if Paul add a note saying that if the Linux installation is modified in any special way the web apps may not run? Do you expect Xojo to buy hosting with your provider and expend X amount of time just to fix this for you?

    Don't get me wrong, I'm not defending Xojo, 2018 version is far from perfect, what I'm trying to say, if I were you I'll try to give Xojo more information/tools and even access to the VPS (a new installation for them to try).

    If you can't help them try in your environment and they don't have access to it, they won't be able to see if they can change something in their end to make the web apps work.

    I don't know if Xojo 2018 is having problems with the 'specially-modified kernel' only, or other things that your VPS changed, so I think is vital that Xojo Inc can test with your VPS, they do have the option to say that they don't support modified installations.

    Really I'm sorry, I do hope that a later version of Xojo will work with your host provider, but what is happening now is that the latest release at this point doesn't work.

  13. Alexandre C

    Jun 23 Pre-Release Testers, Xojo Pro Brazil
    Edited 3 months ago

    @Alberto D;Poo Will you be less angry if Paul add a note saying that if the Linux installation is modified in any special way the web apps may not run?

    Yes! Of course, yes!

    I really can't accept i'm using a 2017 version and after an upgrade to 2018, the app does not work!
    It's like you update your "windows" and it stops to work because this new version does not work with a specific sound card or another thing. (AND THERE ARE NO INFORMATION ABOUT THIS ANY WHERE)

    @Alberto D;Poo Do you expect Xojo to buy hosting with your provider and expend X amount of time just to fix this for you?

    Just for me?… I think if you wait some weeks or months, other users will may have the same problems. They din't notice yet, because they didn't updat their projects with 2018 version…

    @Alberto D;Poo if I were you I'll try to give Xojo more information/tools and even access to the VPS (a new installation for them to try).

    No one asked my access to my VPS. It can be made! My provider has a 30-day trial vps… No problem at all.
    I also talked them about this, and they are very flexible and want to help!

    Alex

  14. brian f

    Jun 23 Pre-Release Testers, Xojo Pro Chilly California

    I can see adding a note in the docs about supported OS versions of Linux using custom Kernels and/or custom libraries not being supported.

    I just cannot blame Xojo for this for not dedicating time and support for this. I would start looking for a new provider

  15. Alexandre C

    Jun 24 Pre-Release Testers, Xojo Pro Brazil

    @brian f I would start looking for a new provider

    So then on version 2018r2, they will not be compatible with something else and then i'll need to move again?…

    Unacceptable.

  16. brian f

    Jun 24 Pre-Release Testers, Xojo Pro Chilly California

    I feel your pain but now that you know the answer you can make sure these questions are answered by your next provider

  17. Alexandre C

    Jun 25 Pre-Release Testers, Xojo Pro Brazil
    Edited 3 months ago

    I disagree.

    I can't change from provider to provider all the time xojo launches a new version!

  18. Ralph A

    Jun 25 Santa Monica, California

    I don't think you would be dealing with this if you use the provider that is Xojo-oriented, like XojoCloud or ServerWarp. I just can't imagine Xojo Inc can keep up with all the possible Linux distributions and flavors of kernels.

  19. brian f

    Jun 25 Pre-Release Testers, Xojo Pro Chilly California

    @Alexandre C I disagree.

    I can't change from provider to provider all the time xojo launches a new version!

    We are not talking about Xojo here. It is about a provider that creates custom kernels and who knows what other custom library's

  20. Tim J

    Jun 26 Pre-Release Testers, Xojo Pro Dehydrating in AZ
    Edited 3 months ago

    @Alexandre C I disagree.

    I can't change from provider to provider all the time xojo launches a new version!

    Was there no more output in the strace than what you provided above? That seems very "small" compared to my average strace runs.

    I also think that the whole cPanel discussion is a red herring.

  21. 2 months ago

    Charles W

    Jul 11 Pre-Release Testers, Xojo Pro Virginia

    Hi all,

    For what it's worth, I just had exactly the same problem but on a different host. I'm using AWS Amazon Linux 2, which is based on Red Hat Enterprise Linux (but it's a whole lot cheaper than RHEL to run in AWS). The message I got was:

    error while loading shared libraries: libunwind.so.8: cannot open shared object file: No such file or directory

    I solved it by running this command:

    sudo yum install libunwind

    This is with a 64-bit Linux web app built with Xojo 2018r1.1

    I hope this helps someone.

or Sign Up to reply!