Tried to install webtop. Got an error with epel repo, when I tried to install nethserver-web on gui. On command line “yum install @nethserver-web” worked. Now I need to install php-imap. Changing nethserver-web fails. epel repo fails also. Installation of webtop fails, because it needs php-imap.
So what to do?? Can anybody help me?
from messages log:
Jul 22 13:02:03 ns7b1 pkgaction[16796]: [YumRPMCheckError] [u’FEHLER bei Transaktionspr\xfcfung gegen\xfcber Depsolve:’, ‘php-imap is needed by nethserver-webtop4-1.3.0-1.ns7.noarch’]
One of the configured repositories failed (Unknown),
and yum doesn’t have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work “fix” this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Disable the repository, so yum won't use it by default. Yum will then
just ignore the repository until you permanently enable it again or use
--enablerepo for temporary usage:
yum-config-manager --disable <repoid>
4. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true
Cannot retrieve metalink for repository: epel/x86_64. Please verify its path and try again
epel is enabled:
[epel]
name=Extra Packages for Enterprise Linux 7 - $basearch
enablegroups=0
#baseurl=http://download.fedoraproject.org/pub/epel/7/$basearch
mirrorlist=https://mirrors.fedoraproject.org/metalink?repo=epel-7&arch=$basearch
failovermethod=priority
enabled=1
gpgcheck=1
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7
if I enable baseurl and disable mirrorlist it works!!
seems to be a problem of epel-mirrors. maybe a temporary failure?
Great job on the beta so far. I’m new to Nethserver (though I did run an e-smith server back in the day) and am considering updating my aging ClearOS server to Nethserver 7. So, I’ve been doing some experimenting and testing for a bit and hit a wall. I don’t know if it’s a bug or something I’m doing wrong, but for the life of me I can’t get nethserver-dc to work properly. Here is some background information on the setup and what I’ve done so far:
Nethserver 7 beta 1 is running in VirtualBox.
Only the base system is installed and updates applied.
Server has a static IP and default root password is changed.
nethserver-dc installs properly; I see no errors in the log.
A bridge is created on the green interface (via the checkbox) and I used a different IP than the server’s.
As the install is finishing up, I get a red error box at the top of the web page and this in the log:
Jul 27 11:38:16 amiga systemd-nspawn: Failed to create directory /var/lib/machines/nsdc//sys/fs/selinux: No such file or directory
Jul 27 11:38:16 amiga systemd-nspawn: Failed to create directory /var/lib/machines/nsdc//sys/fs/selinux: No such file or directory
Jul 27 11:38:40 amiga systemd: Started Authorization Manager.
Jul 27 11:38:40 amiga realmd: * Resolving: _ldap._tcp.kuntzilla.com
Jul 27 11:38:40 amiga realmd: * Performing LDAP DSE lookup on: 192.168.67.23
Jul 27 11:38:40 amiga realmd: ! Can’t contact LDAP server
Jul 27 11:38:40 amiga esmith::event[2805]: realm: Cannot join this realm
Jul 27 11:38:40 amiga esmith::event[2805]: [ERROR] DC join failed
Jul 27 11:38:40 amiga esmith::event[2805]: Action: /etc/e-smith/events/nethserver-dc-save/S96nethserver-dc-join FAILED: 1 [2.949292]
Jul 27 11:38:51 amiga esmith::event[2805]: Event: nethserver-dc-save FAILED
Not wanting to just give up, I found Davide’s nethserver-dc docs and followed the steps to join the AD domain manually. That worked and I got the expected output he shows in the doc right up to the “net ads info” command. That fails with the following:
ads_connect: No logon servers
ads_connect: No logon servers
Didn’t find the ldap server!
I don’t see anything about it in /var/log/messages. Clicking the “Domain Accounts” option in server manager gives similar output:
ads_connect: No logon servers
ads_connect: No logon servers
Didn’t find the ldap server!
ads_connect: No logon servers
Join to domain is not valid: No logon servers
Trying to create a new user with the server manager results in a red error box at the top of the page with the message “User name The user already exists”. I wasn’t ever prompted for a user name
Any ideas or hints? Seems like it shouldn’t be this hard… If I need to fill our a bug report or provide more information please let me know. I’m happy to help out if I can.
Thanks!
Hi @chuckk, welcome here.
I had a similar problem with virtualbox. I had to set the interface to promiscuos mode “allow all”. This is mandatory in a virtualbox setup. Found that yesterday . Maybe this helps in your case also.
Strange behavior of SOGo3 on NS7.
When I login Sogo with a user created on GUI I was not able to create an imap-account. If I did so, login stucked in mailbox0. I created a local user on the machine. After that I was able to use an imap-account on my ISP’S server. If I create a user with GUI the command cat /etc/pwasswd does’t show this user. Is this meant to this way, because of ldap-server in the container?
Also, had issues where the ethernet interfaces were configured, but always had to issue a manual “ifconfig up” to them before they could be used. I’m going to try another couple of installs to see if I can narrow down the circumstances.
I can confirm also the problem reported by @GG_jr and @EddieA about genRandomHash.
The correct util.pm file was named util.pm.mod, therefore any call is still looking at the old file. The solution is to rename util.pm.mod to util.pm:
cd /usr/share/perl5/vendor_perl/esmith/
mv util.pm.mod util.pm
After that, a reinstall of the affected packages should work as expected.