Hello!
have installed the new cockpit today for testing and may say wowwwww!
Something habituation needs but just awesome!
greetings
Gerald
3 Likes
Iāve a Ooops 
Java console says:
Could not realize an impact. Just this āOoopsā.
EDIT: Itās the Softwarecenter. No updates are found in cockpit.
If Iād read read the above, Iād seen it. 
Thank you Ralf, I will try to reproduce.
Could you please paste the output from the command reported inside the console (echo ...).
Just cut&paste it in a shell to get the output.
@edoardo_spadoni could you please take a look?
`echo ā{āactionā:ālist-updatesā}ā | /usr/bin/sudo /usr/libexec/nethserver/api/system-packages/read | jq
{
āhintsā: {
ācountā: 0
},
ānethserver_upgradeā: 0,
āupdatesā: []
}
2 Likes
There is a missing check on object attributes, thank you @flatspin, fixed 
3 Likes
Fix released: nethserver-cockpit-0.1.1-1.ns7.noarch.rpm
3 Likes
Installed the 1.0.1 Version is working the backup!!! Yupiiee!
My test-vm is on 7.6 beta 2 with release-lock.
Canāt get cockpit-0.1.1.-1. update.
Also with release-unlocked.
Which repo to use?
Sorry, something broke on the RPM publications.
The package is now on the master mirror, you can wait for repo sync or download directly from it: http://packages.nethserver.org/nethserver/7.6.1810/updates/x86_64/Packages/nethserver-cockpit-0.1.1-1.ns7.noarch.rpm
I just installed the latest version as per instructions, but I get the oopsā¦
Waited for repo sync. Update done. No more Ooops! 
Check for update works.
@LayLow are you sure you are on Version 0.1.1-1? On my side it works.
rpm -qa nethserver-cockpit
nethserver-cockpit-0.1.1-1.ns7.noarch[root@srv01 ~]# rpm -q nethserver-cockpit
nethserver-cockpit-0.1.0-1.ns7.noarch
Now doing a yum update --enablerepo=nethserver-testing (again)
Seems a mid air collisionā¦
1 Like
I think you donāt have to enable testing repo. Itās in base repo.
This is waht I did a mere few hour ago (Itlay was sleeping )
yum update --enablerepo=nethserver-testing
I truly believe a more robust transition and upgrade path is required.
So, as soon as ns 7.6 is fully released, weāll be able to get the
new server manager as alpha product for testing? Since my previous
experiences with kockpit itself werenāt that great, at least not during the short time I tryed. (main culprate was the services page) Iām all for
second chances. What I do wonder though, is
Since the current server manager doesnāt throw up any hardships
(or I have yet to encounter them:) ) in at least ff and chrome for
windows, combined with screen reading software, will reporting
such events be helpful / apriciated. In all likelyhood a strange
thing to ask, but Iād like to get a clear idea of what can and
canāt be reported later on to keep things useful.
Not sure why, but I just now saw the first post in this topic, so an edit was in order to take out things that have already been answered. Not switching over to the ātest branchā because donāt have a second system for testing, and vmās arenāt yet possible until I find someone to go through the bios with me to turn on the required virtualisation components. So, Iām sort of, looking foward to 7.6 release, even though I not so much like new things, but with an early start things might actually surpass current system and improve upon themā¦ who knows.
Iām not sure about what are you asking for, but you can install cockpit alongside the old server manager.
1 Like
[root@backup ~]# git clone git@github.com:NethServer/nethserver-cockpit
Cloning into ānethserver-cockpitāā¦
Warning: Permanently added the RSA host key for IP address ā140.82.118.3ā to the list of known hosts.
Permission denied (publickey).
fatal: Could not read from remote repository.Please make sure you have the correct access rights
and the repository exists.
[root@backup ~]#
why?
Maybe you donāt have your SSH public key published to Github?
In this case, use http protocol for cloning:
git clone https://github.com/NethServer/nethserver-cockpit.git
1 Like
thank you, now itās ok
1 Like
Is the hotsync app not working anymore in the actual cockpit?