08-22-2018, 12:26 AM
08-22-2018, 12:41 AM
copy and paste the ssh terminal info as your screenshot is not showing...
Also post output from command "moslog"
Also post output from command "moslog"
08-22-2018, 12:45 AM
(08-22-2018, 12:41 AM)DRONE7 Wrote: [ -> ]copy and paste the ssh terminal info as your screenshot is not showing...
Ah, did it make it this time?
[attachment=182]
08-22-2018, 11:26 PM
(08-22-2018, 12:41 AM)DRONE7 Wrote: [ -> ]Also post output from command "moslog"
Here you go:
Code:
pi@moOde:~ $ moslog
// COMPONENT 2 - Auto-shuffle
//
////////////////////////////////////////////////////////////////
** Build Auto-shuffle
Cloning into 'ashuffle'...
fatal: unable to access 'https://github.com/Joshkunz/ashuffle.git/': gnutls_handshake() failed: Error in the pull function.
** Error: Git clone failed
** Error: image build exited
** Error: reboot to resume the build08-23-2018, 12:59 AM
No issues from my home network
pi@rp3:~ $ sudo git clone https://github.com/Joshkunz/ashuffle.git
Cloning into 'ashuffle'...
remote: Counting objects: 259, done.
remote: Total 259 (delta 0), reused 0 (delta 0), pack-reused 259
Receiving objects: 100% (259/259), 50.10 KiB | 0 bytes/s, done.
Resolving deltas: 100% (163/163), done.
pi@rp3:~ $
-Tim
pi@rp3:~ $ sudo git clone https://github.com/Joshkunz/ashuffle.git
Cloning into 'ashuffle'...
remote: Counting objects: 259, done.
remote: Total 259 (delta 0), reused 0 (delta 0), pack-reused 259
Receiving objects: 100% (259/259), 50.10 KiB | 0 bytes/s, done.
Resolving deltas: 100% (163/163), done.
pi@rp3:~ $
-Tim
08-24-2018, 01:26 AM
(08-23-2018, 12:59 AM)Tim Curtis Wrote: [ -> ]No issues from my home network
pi@rp3:~ $ sudo git clone https://github.com/Joshkunz/ashuffle.git
Cloning into 'ashuffle'...
remote: Counting objects: 259, done.
remote: Total 259 (delta 0), reused 0 (delta 0), pack-reused 259
Receiving objects: 100% (259/259), 50.10 KiB | 0 bytes/s, done.
Resolving deltas: 100% (163/163), done.
pi@rp3:~ $
-Tim
For me the in-place update from 4.1 to 4.2 failed with the messages outlined above, but a fresh installation went fine. The first 4.2 update went perfectly, now listening to Amy's.
Thanks for all this,
John