[vmchecker-request] Probleme vmechcker

[Cristian Chilipirea]

Dude... come on... give me more than this. E corupt, inseamna ca e recent
ca anul trecut a mers perfect, pana si semestrul trecut a mers perfect ca
la APD folosim aceeasi masina.
What do I need to do to fix it? Eu mereu am folosit VM dat de voi, cel de
la so...
Macar hai sa facem un skype ceva, sa discutam despre cum ar trebui facute
chestiile astea ca sa nu te mai buzai in viitor. Manageuiesc deja la 3
materii teme pe vmechecker si mereu ma lovesc de cate o porcarie... Trebuie
sa facem ceva sa eficientizam discutile astea ca cate un raspuns de o linie
merg greu lucrurile...

2016-02-08 23:33 GMT+02:00 Valentin Gosu <valentin.gosu at gmail.com>:

> Cel mai probabil VMul este corupt.
>
> 2016-02-08 22:28 GMT+01:00 Cristian Chilipirea <
> cristian.chilipirea at gmail.com>:
>
>> Am verificat merge ssh in ambele directii
>> ssh apd at checker
>> ssh proto at vmchecker.cs.pub.ro
>> Ambele merg fara parola, presupun ca asta ar trebui.
>> Acuma primesc
>>
>> vmexecutor exitcode 1 (error)
>>
>>
>> 2016-02-08 23:21 GMT+02:00 Valentin Gosu <valentin.gosu at gmail.com>:
>>
>>> Trebuie pusa cheia publica si invers. apd at checker -> proto at vmchecker
>>> /authorized_keys
>>>
>>> 2016-02-08 22:18 GMT+01:00 Cristian Chilipirea <
>>> cristian.chilipirea at gmail.com>:
>>>
>>>> Logarea pare sa mearga acum si in coada tema apare cum trebuie... doar
>>>> ca nu pare sa creeze fisierele de output. Any ideas?
>>>>
>>>> 2016-02-08 23:14 GMT+02:00 Valentin Gosu <valentin.gosu at gmail.com>:
>>>>
>>>>> Incearca acum ssh apd at checker.cs.pub.ro
>>>>>
>>>>> 2016-02-08 22:12 GMT+01:00 Cristian Chilipirea <
>>>>> cristian.chilipirea at gmail.com>:
>>>>>
>>>>>> Also eu nu cred ca am access la checker. So tot am nevoie de ajutorul
>>>>>> vostru pentru acele setari.
>>>>>>
>>>>>> 2016-02-08 23:10 GMT+02:00 Cristian Chilipirea <
>>>>>> cristian.chilipirea at gmail.com>:
>>>>>>
>>>>>>> OK!
>>>>>>> Any of the 2 works for me. Dar anul trecut a mers fara probleme cu
>>>>>>> userul de apd, so nu imi e clar de ce acum nu mai merge.
>>>>>>>
>>>>>>> 2016-02-08 23:07 GMT+02:00 Valentin Gosu <valentin.gosu at gmail.com>:
>>>>>>>
>>>>>>>> In cazul asta exista 2 solutii:
>>>>>>>> 1. preferabil sa facem un user nou pe checker, cu VM separat, etc
>>>>>>>> 2. putem adauga cheile proto at vmchecker la authorized_keys pe
>>>>>>>> checker, si invers. Ar trebui sa mearga pentru moment.
>>>>>>>>
>>>>>>>> 2016-02-08 22:02 GMT+01:00 Cristian Chilipirea <
>>>>>>>> cristian.chilipirea at gmail.com>:
>>>>>>>>
>>>>>>>>> Just to clarify, userul este proto
>>>>>>>>>
>>>>>>>>> 2016-02-08 23:01 GMT+02:00 Cristian Chilipirea <
>>>>>>>>> cristian.chilipirea at gmail.com>:
>>>>>>>>>
>>>>>>>>>> Salut,
>>>>>>>>>>
>>>>>>>>>> Daca te refereai la problema mea cred ca ai gresit materia.
>>>>>>>>>> La mine problema e la protocoale de comunicatie. Foloseste uerul
>>>>>>>>>> de apd.
>>>>>>>>>>
>>>>>>>>>> Cu bine,
>>>>>>>>>> Cristian
>>>>>>>>>>
>>>>>>>>>> 2016-02-08 22:59 GMT+02:00 Valentin Gosu <valentin.gosu at gmail.com
>>>>>>>>>> >:
>>>>>>>>>>
>>>>>>>>>>> Salut Razvan,
>>>>>>>>>>>
>>>>>>>>>>> Din cate am observat, config-ul PC incearca sa foloseasca
>>>>>>>>>>> user-ul SO pe checker.
>>>>>>>>>>> Exista si un user pentru pc, insa nu checker-ul nu este
>>>>>>>>>>> initializat.
>>>>>>>>>>> Din pacate nu o sa reusesc sa aranjez totul in seara aceasta.
>>>>>>>>>>> Crezi ca poti sa te ocupi tu?
>>>>>>>>>>>
>>>>>>>>>>> Mersi
>>>>>>>>>>>
>>>>>>>>>>> 2016-02-08 20:22 GMT+01:00 Cristian Chilipirea <
>>>>>>>>>>> cristian.chilipirea at gmail.com>:
>>>>>>>>>>>
>>>>>>>>>>>> small reminder
>>>>>>>>>>>>
>>>>>>>>>>>> 2016-02-08 17:45 GMT+02:00 Mihai Carabas <
>>>>>>>>>>>> mihai.carabas at gmail.com>:
>>>>>>>>>>>>
>>>>>>>>>>>>> Trebuie sa creeze vali acces pentru ASC.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Pentru fep.grid.pub.ro, iti creez diseara cont in LDAP.
>>>>>>>>>>>>>
>>>>>>>>>>>>> 2016-02-08 16:54 GMT+02:00 Valentin Gosu <
>>>>>>>>>>>>> valentin.gosu at gmail.com>:
>>>>>>>>>>>>> > O sa incerc sa ma uit in seara asta.
>>>>>>>>>>>>> > Foarte posibil nu sunt cheile setate cum trebuie.
>>>>>>>>>>>>> >
>>>>>>>>>>>>> > 2016-02-08 15:52 GMT+01:00 Cristian Chilipirea
>>>>>>>>>>>>> > <cristian.chilipirea at gmail.com>:
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> Salut,
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> Am vrut sa implementez tema pe vmechecker la protocoale.
>>>>>>>>>>>>> >> Am primit eroarea urmatoare cand fac upload
>>>>>>>>>>>>> >> "errorTrace": "Traceback (most recent call last):\n File
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> \"/usr/local/lib/python2.7/dist-packages/vmchecker/websutil.py\", line 239,
>>>>>>>>>>>>> >> in get_test_queue_contents\n look_for_keys=False)\n File
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> \"/usr/local/lib/python2.7/dist-packages/paramiko/client.py\", line 353, in
>>>>>>>>>>>>> >> connect\n raise BadHostKeyException(hostname, server_key,
>>>>>>>>>>>>> >> our_server_key)\nBadHostKeyException: ('checker.cs.pub.ro',
>>>>>>>>>>>>> , )
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> Presupun ca nu merge masina pe care se fac testele.
>>>>>>>>>>>>> >> Puteti va rog sa verificati?
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> @Mihai - o sa am nevoie de access la vmchecker pentru ASC.
>>>>>>>>>>>>> Daca vad eu
>>>>>>>>>>>>> >> bine nici nu exista materia acolo. Deasemenea o sa am
>>>>>>>>>>>>> nevoie de userul asc
>>>>>>>>>>>>> >> pe fep ca sa pot sa arunc temele cu openCL pe masinile de
>>>>>>>>>>>>> acolo.
>>>>>>>>>>>>> >>
>>>>>>>>>>>>> >> Cu bine,
>>>>>>>>>>>>> >> Cristian Chilipirea
>>>>>>>>>>>>> >
>>>>>>>>>>>>> >
>>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cursuri.cs.pub.ro/pipermail/vmchecker-request/attachments/20160208/95a97fb3/attachment-0001.html>