I've confirmed it's not the time/date sync. It's not a firewall. It's not the software version, it does not work in 3.0, 3.2.2 or even 3.2.3-rc1.
Can it be the domain in which machines are? The windows one has no domain asociated. I don't see how can this relate to the error but... The error is this one: "SSL_connect SYSCALL returned=5 errno=0 state=SSLv2/v3 read server hello A" This happens once the client cert is signed in the puppetmaster. El martes, 2 de julio de 2013 18:16:43 UTC+2, Álvaro Acción - CiTIUS escribió: > > A little update. I don't know the real reason behind the problem, but it > seems that after changing the network address of the server the problem has > suddenly dissapeared. The trace I pasted is the only clue I've got. > > Now I get a error when calling fork(), but it's a known bug and has > already a temporal solution. > And after that one, a SSL error. I'm not at work no so I'll try to update > tomorrow with more info. > > Thanks! > -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-users+unsubscr...@googlegroups.com. To post to this group, send email to puppet-users@googlegroups.com. Visit this group at http://groups.google.com/group/puppet-users. For more options, visit https://groups.google.com/groups/opt_out.
