Benjamin Mahler created MESOS-872:
-------------------------------------

             Summary: FaultToleranceTest.SlaveReliableRegistration runs forever.
                 Key: MESOS-872
                 URL: https://issues.apache.org/jira/browse/MESOS-872
             Project: Mesos
          Issue Type: Bug
          Components: test
            Reporter: Benjamin Mahler


[ RUN      ] FaultToleranceTest.SlaveReliableRegistration
I1205 19:50:19.203596 27059 master.cpp:284] Master started on 127.0.1.1:38685
I1205 19:50:19.203963 27059 master.cpp:298] Master ID: 
201312051950-16842879-38685-27037
I1205 19:50:19.203977 27059 master.cpp:301] Master only allowing authenticated 
frameworks to register!
I1205 19:50:19.203675 27056 slave.cpp:112] Slave started on 42)@127.0.1.1:38685
I1205 19:50:19.204273 27056 slave.cpp:212] Slave resources: cpus(*):2; 
mem(*):1024; disk(*):1024; ports(*):[31000-32000]
I1205 19:50:19.203835 27060 sched.cpp:207] New master detected at 
[email protected]:38685
I1205 19:50:19.204417 27060 sched.cpp:260] Authenticating with master 
[email protected]:38685
I1205 19:50:19.205493 27056 state.cpp:33] Recovering state from 
'/tmp/FaultToleranceTest_SlaveReliableRegistration_NDpL1G/meta'
I1205 19:50:19.205571 27056 status_update_manager.cpp:186] Recovering status 
update manager
I1205 19:50:19.205631 27056 slave.cpp:2759] Finished recovery
I1205 19:50:19.205685 27056 slave.cpp:497] New master detected at 
[email protected]:38685
I1205 19:50:19.205725 27056 slave.cpp:524] Detecting new master
W1205 19:50:19.206559 27059 master.cpp:1335] Ignoring register slave message 
from precise since not elected yet
I1205 19:50:19.206615 27059 status_update_manager.cpp:160] New master detected 
at [email protected]:38685
I1205 19:50:19.206672 27059 hierarchical_allocator_process.hpp:302] 
Initializing hierarchical allocator process with master : [email protected]:38685
I1205 19:50:19.206697 27059 master.cpp:84] No whitelist given. Advertising 
offers for all slaves
I1205 19:50:19.206812 27059 master.cpp:746] The newly elected leader is 
[email protected]:38685
I1205 19:50:19.206825 27059 master.cpp:750] Elected as the leading master!
I1205 19:50:19.207381 27060 sched.cpp:229] Detecting new master
I1205 19:50:19.207423 27060 authenticatee.hpp:124] Creating new client SASL 
connection
I1205 19:50:19.207547 27060 master.cpp:1843] Authenticating framework at 
scheduler(60)@127.0.1.1:38685
I1205 19:50:19.207618 27060 authenticator.hpp:140] Creating new server SASL 
connection
I1205 19:50:19.207712 27060 authenticatee.hpp:212] Received SASL authentication 
mechanisms: CRAM-MD5
I1205 19:50:19.207730 27060 authenticatee.hpp:238] Attempting to authenticate 
with mechanism 'CRAM-MD5'
I1205 19:50:19.207752 27060 authenticator.hpp:243] Received SASL authentication 
start
I1205 19:50:19.207782 27060 authenticator.hpp:325] Authentication requires more 
steps
I1205 19:50:19.207880 27060 authenticatee.hpp:258] Received SASL authentication 
step
I1205 19:50:19.207921 27060 authenticator.hpp:271] Received SASL authentication 
step
I1205 19:50:19.207937 27060 auxprop.cpp:81] Request to lookup properties for 
user: 'test-principal' realm: 'precise' server FQDN: 'precise' 
SASL_AUXPROP_VERIFY_AGAINST_HASH: false SASL_AUXPROP_OVERRIDE: false 
SASL_AUXPROP_AUTHZID: false
I1205 19:50:19.207943 27060 auxprop.cpp:153] Looking up auxiliary property 
'*userPassword'
I1205 19:50:19.207953 27060 auxprop.cpp:153] Looking up auxiliary property 
'*cmusaslsecretCRAM-MD5'
I1205 19:50:19.207962 27060 auxprop.cpp:81] Request to lookup properties for 
user: 'test-principal' realm: 'precise' server FQDN: 'precise' 
SASL_AUXPROP_VERIFY_AGAINST_HASH: false SASL_AUXPROP_OVERRIDE: false 
SASL_AUXPROP_AUTHZID: true
I1205 19:50:19.207967 27060 auxprop.cpp:103] Skipping auxiliary property 
'*userPassword' since SASL_AUXPROP_AUTHZID == true
I1205 19:50:19.207973 27060 auxprop.cpp:103] Skipping auxiliary property 
'*cmusaslsecretCRAM-MD5' since SASL_AUXPROP_AUTHZID == true
I1205 19:50:19.207981 27060 authenticator.hpp:317] Authentication success
I1205 19:50:19.208006 27060 authenticatee.hpp:298] Authentication success
I1205 19:50:19.208024 27060 master.cpp:1883] Successfully authenticated 
framework at scheduler(60)@127.0.1.1:38685
I1205 19:50:19.208076 27060 sched.cpp:334] Successfully authenticated with 
master [email protected]:38685
I1205 19:50:19.208114 27060 master.cpp:801] Received registration request from 
scheduler(60)@127.0.1.1:38685
I1205 19:50:19.208207 27060 master.cpp:819] Registering framework 
201312051950-16842879-38685-27037-0000 at scheduler(60)@127.0.1.1:38685
I1205 19:50:19.208261 27060 sched.cpp:383] Framework registered with 
201312051950-16842879-38685-27037-0000
I1205 19:50:19.208279 27060 sched.cpp:397] Scheduler::registered took 7261ns
I1205 19:50:19.208302 27060 hierarchical_allocator_process.hpp:332] Added 
framework 201312051950-16842879-38685-27037-0000
I1205 19:50:19.208310 27060 hierarchical_allocator_process.hpp:726] No 
resources available to allocate!
I1205 19:50:19.208315 27060 hierarchical_allocator_process.hpp:688] Performed 
allocation for 0 slaves in 5801ns
Build timed out (after 180 minutes). Marking the build as failed.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Reply via email to