Thanks all for your ideas, jumping to 2.5 (with self-compiled packages
without munge) seems to me like a good plan.
BR/Pablo
On 08/28/2012 01:03 PM, André Gemünd wrote:
> Hi,
>
> we use an adapted spec from epel (for the same titles) and put the files into a custom repo which is preferred by yum-plugin-priorities. Higher release numbers should work the same. In that way, you don't need rpm or excludes.
>
> Greetings
> Andre
>
> ----- Ursprüngliche Mail -----
>> On Mon, 27 Aug 2012 14:13:29 +0200
>> Erekle Magradze wrote:
>>
>>> Hi Arnau,
>> Hi,
>>
>>> I have installed the EMI2 cream and when I am running qstat, I get
>>> munge: Error: Unable to access "/var/run/munge/munge.socket.2": No
>>> such file or directory
>>> qstat: End of File
>> Well, we're running EMI1, but the "receipt" must be the same.
>>
>>> I've checked and on our pbs server there is no munge installed,
>>> could
>>> you please share how did you installed the EMI cream without munge?
>> the problem is that emi-cream install *torque* packages from epel
>> (which are compiled with munge support). So, you must remove those
>> packages and add self-compiled ones (use rpm instead of yum).
>>
>> ** In our case, epel repo has an exclude of torque packages, so those
>> one are never installed. those repos are managed under puppet.
>>
>>> Thank you in advance
>>> Cheers
>>> Erekle
>> HTH,
>> Arnau
>>
|