Re: [gentoo-user] Again a small embedded arch problem with Gentoo

2015-11-29 Thread Alec Ten Harmsel



On 2015-11-29 06:57, meino.cra...@gmx.de wrote:

Hi,

two "identical" (better read: expected to be identical... ;)


Just a quick suggestion - you should use ansible or puppet to keep them 
in sync.



Arietta
G25 tiny embedded systems have a Gentoo installed each. Both are
updated always at the same time.
On both I copied the same source of VIM (git repo) and tried to
update the local repo than.

One said:
Arietta G25 B:CVS-Archive/VIM>./update.sh
Already up-to-date.

(ok, nice and fine)

but the other said:
fatal: unable to access 'https://github.com/vim/vim.git/': SSL certificate 
problem: certificate has expired
[1]1983 exit 1 ./update.sh



What is the date on the board that failed? The only thing I can think of 
is that

the date is incorrect, and far enough off to cause an SSL error.

Alec



Re: [gentoo-user] Again a small embedded arch problem with Gentoo

2015-11-29 Thread Meino . Cramer
Alec Ten Harmsel  [15-11-29 13:16]:
> 
> 
> On 2015-11-29 06:57, meino.cra...@gmx.de wrote:
> >Hi,
> >
> >two "identical" (better read: expected to be identical... ;)
> 
> Just a quick suggestion - you should use ansible or puppet to keep them 
> in sync.
> 
> >Arietta
> >G25 tiny embedded systems have a Gentoo installed each. Both are
> >updated always at the same time.
> >On both I copied the same source of VIM (git repo) and tried to
> >update the local repo than.
> >
> >One said:
> >Arietta G25 B:CVS-Archive/VIM>./update.sh
> >Already up-to-date.
> >
> >(ok, nice and fine)
> >
> >but the other said:
> >fatal: unable to access 'https://github.com/vim/vim.git/': SSL 
> >certificate problem: certificate has expired
> >[1]1983 exit 1 ./update.sh
> >
> 
> What is the date on the board that failed? The only thing I can think 
> of is that
> the date is incorrect, and far enough off to cause an SSL error.
> 
> Alec
> 

Hi Alec,

oh YEAH! Thats's it! The ntp-sync command seems to have failed...
The system time said 19.Oct.2015 (which is not the usual 1.1.1970)
I resynced the time and and the problem is gone!
Thanks! :)

Best regards,
Meino