> Am 18.01.2019 um 18:06 schrieb David Triimboli <trimb...@cshl.edu>: > > On 1/18/2019 11:49 AM, Reuti wrote: >>> Am 18.01.2019 um 17:41 schrieb David Triimboli <trimb...@cshl.edu>: >>> >>> On 1/18/2019 11:22 AM, Reuti wrote: >>>> Hi, >>>> >>>>> Am 18.01.2019 um 17:09 schrieb David Triimboli <trimb...@cshl.edu>: >>>>> >>>>> Hi, all. I've got a twenty-four-node cluster running versions of CentOS 5 >>>>> and Sun Grid Engine. This cluster desperately needs its node OSes >>>>> upgraded to be able to install newer software packages, a job I've been >>>>> tasked with. The users want to put Ubuntu on the nodes. >>>>> >>>>> I've been working in virtual machines, trying to get some form of grid >>>>> engine to work. My understanding is that the old Sun Grid Engine simply >>>>> won't work in any modern Linux kernel. Ubuntu 18.04 has a bunch of Son of >>>>> Grid Engine packages available through apt-get, but I haven't been able >>>>> to get these to work — the services won't run. All instructions I have >>>>> found on the web seem to be old and just don't work. I'm even willing to >>>>> consider Univa Grid Engine — but they never responded to my request for >>>>> trial software. >>>>> >>>>> How should I proceed? What grid engine can I install that will work on a >>>>> modern Ubuntu distribution? What tricks do I need to know to get it to >>>>> work. Can someone point me to something to get me started? >>>> I would assume that most likely the `arch` script inside SGE isn't >>>> prepared for your actual kernel, i.e. a case for 4.* kernels is missing. >>>> What does: >>>> >>>> $ $SGE_ROOT/util/arch >>>> >>>> return? >>> >>> If I install the packages available through apt-get, >>> /usr/share/gridengine/util/arch returns: lx-amd64. >> This is fine. >> >> If the startup fails, there are usually some message in file in /tmp called >> qmasterd.$PID or beginning with execd.$PID alike. Can you spot anything >> there? > > > There are no such files in /tmp, indeed, no files called qmasterd* anywhere > in the filesystem. > > The grid engine logging seems to happen in /var/spool/gridengine. In > qmaster/messages, I have: > > ---BEGIN QUOTE--- > 01/18/2019 11:37:41| main|ubuntuclient1|W|local configuration ubuntuclient1 > not defined - using global configuration > 01/18/2019 11:37:41| main|ubuntuclient1|E|global configuration not defined > 01/18/2019 11:37:41| main|ubuntuclient1|C|setup failed > 01/18/2019 11:38:14| main|ubuntuclient1|W|local configuration ubuntuclient1 > not defined - using global configuration > 01/18/2019 11:38:14| main|ubuntuclient1|E|global configuration not defined > 01/18/2019 11:38:14| main|ubuntuclient1|C|setup failed > ---END QUOTE---
I had a brief look at the Debian package. It seems that they provide a setup procedure on their own, which should replace the usual setup. Maybe this wan't triggered here, and hence no configuration is available at all. The setup which is used by SoGE on its own are the two scripts install_qmaster and install_execd (somewhere in /var/lib/gridengine in Debian). These two scripts should prepare there necessary setup, in case Debian ones was skipped. -- Reuti _______________________________________________ users mailing list users@gridengine.org https://gridengine.org/mailman/listinfo/users
