Dear all,
I know, the problem was discusses one or two years before, but I still
have trouble to eliminate messages in.err file:
I'm using SGE 6.2u5 and for every allocated node of an openmpi job the
sge job's error file has two lines like this:
//bin/bash: module: line 1: syntax error: unexpe
Hi,
To eliminate this probelm, we use module like this in our cluster:
1/ the module must be visible in the PATH
2/ we use : #!/bin/bash -l at the begining of the script.
3/ we use -V to export env variables
here is an example of an MPI-SGE script :
#!/bin/bash -l#$ -q mpi.q#$ -V#$ -N test_sge
Schmidt,
I've been having the same problem ever since I upgraded my cluster
nodes to RHEL 6. A few weeks ago. My SGE installation was not touched
during the upgrade, since it's on an NFS partition, and the head node
was not touched during the upgrade, either. The error seems harmless,
and I have
Am 23.11.2011 um 16:01 schrieb Prentice Bisbal:
> Schmidt,
>
> I've been having the same problem ever since I upgraded my cluster
> nodes to RHEL 6. A few weeks ago. My SGE installation was not touched
> during the upgrade, since it's on an NFS partition, and the head node
> was not touched dur
We modified the modules distribution slightly to get around this.
In /usr/share/Modules/init/bash I commented out the 'export -f module' line.
In a normal login shell, modules.sh will be called from profile.d so
the module command is available. In a non login shell, like an app
wrapper script fo
On 11/23/2011 10:10 AM, Reuti wrote:
> Am 23.11.2011 um 16:01 schrieb Prentice Bisbal:
>
>> Schmidt,
>>
>> I've been having the same problem ever since I upgraded my cluster
>> nodes to RHEL 6. A few weeks ago. My SGE installation was not touched
>> during the upgrade, since it's on an NFS part
On 11/28/2011 03:00 PM, Prentice Bisbal wrote:
>
> On 11/23/2011 10:10 AM, Reuti wrote:
>> Am 23.11.2011 um 16:01 schrieb Prentice Bisbal:
>>
>>> Schmidt,
>>>
>>> I've been having the same problem ever since I upgraded my cluster
>>> nodes to RHEL 6. A few weeks ago. My SGE installation was not
Am 28.11.2011 um 21:00 schrieb Prentice Bisbal:
> On 11/23/2011 10:10 AM, Reuti wrote:
>> Am 23.11.2011 um 16:01 schrieb Prentice Bisbal:
>>
>>> Schmidt,
>>>
>>> I've been having the same problem ever since I upgraded my cluster
>>> nodes to RHEL 6. A few weeks ago. My SGE installation was not
On 11/28/2011 07:01 PM, Reuti wrote:
> Am 28.11.2011 um 21:00 schrieb Prentice Bisbal:
>
>> On 11/23/2011 10:10 AM, Reuti wrote:
>>> Am 23.11.2011 um 16:01 schrieb Prentice Bisbal:
>>>
Schmidt,
I've been having the same problem ever since I upgraded my cluster
nodes to RHEL 6.
Am 29.11.2011 um 15:57 schrieb Prentice Bisbal:
> On 11/28/2011 07:01 PM, Reuti wrote:
>> Am 28.11.2011 um 21:00 schrieb Prentice Bisbal:
>>
>>> On 11/23/2011 10:10 AM, Reuti wrote:
Am 23.11.2011 um 16:01 schrieb Prentice Bisbal:
> Schmidt,
>
> I've been having the same p
Resending since original was sent to Reuti, but not the rest of the list.
On 11/29/2011 10:27 AM, Reuti wrote:
> Am 29.11.2011 um 15:57 schrieb Prentice Bisbal:
>
>> On 11/28/2011 07:01 PM, Reuti wrote:
>>> Am 28.11.2011 um 21:00 schrieb Prentice Bisbal:
>>>
On 11/23/2011 10:10 AM, Reuti wrot
Hi,
Am 01.12.2011 um 14:31 schrieb Prentice Bisbal:
>>
>> I finally had some time to dig around on my systems, and here's what I
> found. Some of this will be obvious to experienced RHEL admins/users,
> but I'm just trying to be complete, and provide a full explanation for
> future googlers:
>
On 12/01/2011 09:16 AM, Reuti wrote:
> Hi,
>
> Am 01.12.2011 um 14:31 schrieb Prentice Bisbal:
>
>>>
>>> I finally had some time to dig around on my systems, and here's what I
>> found. Some of this will be obvious to experienced RHEL admins/users,
>> but I'm just trying to be complete, and provi
Prentice Bisbal writes:
> Schmidt,
>
> I've been having the same problem ever since I upgraded my cluster
> nodes to RHEL 6. A few weeks ago. My SGE installation was not touched
> during the upgrade, since it's on an NFS partition, and the head node
> was not touched during the upgrade, either.
On Thu, Dec 1, 2011 at 9:16 AM, Reuti wrote:
> is this really only a multi line problem? I mean: then output of env shows
> something like:
>
> foobar=() { echo yes
> }
>
> but even if you make one line out of it (with an additional ";") it can't be
> defined this way AFAICS:
>
> $ foobar() {
Am 01.12.2011 um 23:11 schrieb Rayson Ho:
> On Thu, Dec 1, 2011 at 9:16 AM, Reuti wrote:
>> is this really only a multi line problem? I mean: then output of env shows
>> something like:
>>
>> foobar=() { echo yes
>> }
>>
>> but even if you make one line out of it (with an additional ";") it c
On Thu, Dec 1, 2011 at 6:41 PM, Reuti wrote:
> I assume you mean "function" instead of "modules" in the paragraph above.
Yup, I am not that good at all those bash specific functionalities...
Thanks for catching that!
> But it's really interesting, as I wasn't aware that bash will try to scan
>
17 matches
Mail list logo
