Hello Fabrice,
many thanks, now it works!
Regards
Hubert
Am 22.02.2016 um 14:34 schrieb Fabrice DURAND:
Hello Hubert,
remove all the trap and whitelisted_categories in violations.conf then do :
/usr/local/pf/bin/pfcmd configreload hard
and restart packetfence.
Regards
Fabrice
Le 2016-02-22
Hello Hubert,
remove all the trap and whitelisted_categories in violations.conf then do :
/usr/local/pf/bin/pfcmd configreload hard
and restart packetfence.
Regards
Fabrice
Le 2016-02-22 07:44, Hubert Kupper a écrit :
> Hello,
>
> after upgrading from pf 5.6.0 to 5.7.0 packetfence starts with t
Hello,
after upgrading from pf 5.6.0 to 5.7.0 packetfence starts with the following
errors:
service packetfence start
Starting PacketFence...Set name-type for VLAN subsystem. Should be visible in
/proc/net/vlan/config
service|command
httpd: apr_sockaddr_info_get() failed for pfence4
httpd: Cou
wmi-1.3.14-4.el6.art.x86_64 is not coming from packetfence repo but from atomic
repo.
So remove wmi, disable epel, atomic repo and reinstall win from packetfence
repo.
Le 27 mai 2015 23:02:23 GMT-04:00, Minh Trung a écrit :
>Hello,
>
>I already installed wmi but seems it not link...
>
>> [root
Hello,
I already installed wmi but seems it not link...
> [root@vmvnnetsec01 ld.so.conf.d]# yum install wmi --enablerepo=packetfence
> Loaded plugins: fastestmirror, refresh-packagekit, security
> Setting up Install Process
> Loading mirror speeds from cached hostfile
> epel/metalink
> | 4.6 kB
OK so first let's go in /etc/ld.so.conf.d and check if there is a
wmi.conf file if no create it and add /lib/python inside and retry ldconfig.
Also to install from packetfence repo you just have to launch yum
install wmi --enablerepo=packetfence
Regards
Fabrice
Le 2015-05-27 21:15, Minh Tru
Hello Fabrice,
Yes, i am using CentOS 6.6
Here is the file that i found:
> [root@vmvnnetsec01 logs]# find / -name libasync_wmi_lib.so.0
> /lib/python/libasync_wmi_lib.so.0
> You have new mail in /var/spool/mail/root
> [root@vmvnnetsec01 logs]# ldconfig
> [root@vmvnnetsec01 logs]#
>
> I can not f
Hello Minh,
i suppose you are running centos.
Did you find this file libasync_wmi_lib.so.0 ?
What happen if you do a ldconfig ?
Did you try to reinstall wmi from PacketFence repo ?
Regards
Fabrice
Le 2015-05-27 04:05, Minh Trung a écrit :
Hello experts,
I did follow as the procedure upgrade
Hello experts,
I did follow as the procedure upgrade docs but after restart all services,
i can not logon to webpage admin.
Here is the some info may helpful:
> /usr/local/pf/bin/pfcmd configreload hard
> Couldn't require pf::api::local : Can't load
> '/usr/lib64/perl5/vendor_perl/auto/Net/WMICli
Does anyone have any suggestions for this?
I'm hoping to set up a fresh install of PF and then import the settings
from a PF 4.7.0 server.
Is this recommended?
Kind regards,
On Thu, 14 May 2015 at 11:16 Steve Allen wrote:
> Hi
>
> I changed the permissions on the logs folder and the pfconfig.
Hi
I changed the permissions on the logs folder and the pfconfig.log file to
777 and when I updated I did not receive the error related to file
permissions.
However, the upgrade still does not seem to have works. I will post the
output below.
Instead of upgrading, how easy is it for me to export
Hi Steve,
The timestamp looks pretty old on that file:
-rw-r--r-- 1 root pf 0 Mar 10 13:23 pfconfig.log
I am not sure where you got it, but try deleting it and restarting.
Regards,
--
Louis Munro
lmu...@inverse.ca :: www.inverse.ca
+1.514.447.4918 x125 :: +1 (866) 353-6153 x125
Inve
Hi Louis
I have just tried the upgrade again and had the same error.
The steps I did are as follows:
- Shutdown server
- Take a snapshot backup
- Started server
- Ran yum update to get the latest security updates etc,
- Reboot server (as a precaution)
- Followed the
https://
Hi Louis
I had to rollback my PF server so its now back on 4.7.0.
I'm hoping to attempt the upgrade again over the next few days so when I do
I'll include more details and logs.
Kind regards
Steve
On Fri, 1 May 2015 18:14 Louis Munro wrote:
> Hi Steve,
> What distro is this on?
>
> How did y
Hi Steve,
What distro is this on?
How did you upgrade precisely?
The issue looks like incorrect permissions on /usr/local/pf/logs/pfconfig.log.
That should be handled by the upgrade though.
Can you show us the output of this?
# ls -l /usr/local/pf/logs/
Regards,
--
Louis Munro
lmu...@inverse.c
Hi I have just upgraded from 4.7.0 to 5.0.1 and now the PacketFence server
is not running.
If I try to restart the service I recieve the following error:
[root@packetfence01 ~]# /etc/init.d/packetfence restart
Starting pfconfig: Can't sysopen /usr/local/pf/logs/pfconfig.log
(Permission denied) at
16 matches
Mail list logo