Displaying 20 results from an estimated 89 matches for "onge".
Did you mean:
one
2007 Oct 24
5
Error while running YUM UPDATE today
error viewed:
Updating : openssl ####################### [ 1/48]
/sbin/ldconfig: /lib/libstdc++-libc6.2-2.so.3 is not an ELF file - it has
the wr
ong magic bytes at the start.
Updating : openssl ####################### [ 1/48]
/sbin/ldconfig: /lib/libstdc++-libc6.2-2.so.3 is not an ELF file - it has
the wr
ong magic bytes at the start.
Any one
2018 Sep 04
2
WinNUT Client Logs
Hi Charles,
Are there any logs generated by the WinNUT client? I'm trying to configure it for the first time and I cannot make it to work. Here are my settings:
Nut.conf
MODE=netclient
Upsmon.conf
MONITOR ups at pfsense 1 <username> <password> slave
MINSUPPLIES 1
SHUTDOWNCMD "C:\\WINDOWS\\system32\\shutdown.exe -s -t 0"
POLLFREQ 5
POLLFREQALERT 5
HOSTSYNC 15
DEADTIME
2018 Aug 30
2
Wrong battery.date variable value [APC, usbhid-ups]
On Aug 30, 2018, at 10:05 AM, Ong, Kevin wrote:
>
> The battery.mfr.date is actually the correct value I'm looking for. That is the exact date the battery was last replaced. And yes, it is the correct value displayed in apcupsd.
I think we're on the same page for the battery date. What about the date of manufacture for the UPS - does 2012 seem reasonable?
>
> For the debug
2018 Sep 07
0
WinNUT Client Logs
Any comments here?
Thank you.
Regards,
Kevin Mychal M. Ong
Sr Infrastructure Engineer, Microsoft Technology Services - Messaging
Global Infrastructure Operations
Ingram Micro Inc.
4F Three World Square, 22 Upper McKinley Hill, Fort Bonifacio
Taguig City, Philippines 1634
Direct +1-716-633-3600 ext. 33996
Mobile +63-917-511-0251
*: kevin.ong at ingrammicro.com<mailto:kevin.ong at
2018 Aug 30
0
Wrong battery.date variable value [APC, usbhid-ups]
Oh, and I forgot to mention that "echo $SHELL" returns /bin/sh for me.
Thank you.
Regards,
Kevin Mychal M. Ong
Sr Infrastructure Engineer, Microsoft Technology Services - Messaging
Global Infrastructure Operations
Ingram Micro Inc.
4F Three World Square, 22 Upper McKinley Hill, Fort Bonifacio
Taguig City, Philippines 1634
Direct +1-716-633-3600 ext. 33996
Mobile
2003 Aug 02
0
Re: how l (PR#3614)
--FE8A9_158F__B2CBD0A46E.
Content-Type: text/html;
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<title>Home Page</title>
</head>
<body>
Howdy R-bugs
<p><font face=3D"Verdana, Arial, Helvetica, sans-serif" size=3D"3"
color=3D=
2018 Aug 15
2
Wrong battery.date variable value
Kevin,
As Matthijs noted, pfSense uses a circular log file. The default size is ~500KB, which can be a bit small. You can increase the log file size by changing the “Log file size” parameter on the Log management page. Look for the wrench symbol on the system log page (Status / System Logs / System / General). Note that you have to clear the log after changing its size. FWIW, I have mine set to
2018 Aug 13
5
Wrong battery.date variable value
> On Aug 13, 2018, at 06:17, Charles Lepple <clepple at gmail.com> wrote:
>
> On Aug 12, 2018, at 11:03 PM, Kevin Mychal M. Ong <kevindd992002 at yahoo.com> wrote:
>>
>> Hi,
>>
>> I installed apcupsd through pfsense and noticed some discrepancy with the NUT package. I'm not sure if this is a bug regarding the BATTDATE (apcupsd) and battery.date
2018 Aug 30
3
Wrong battery.date variable value [APC, usbhid-ups]
...ntrol-C
upsdrvctl start
and then please post the contents of /tmp/APC_BR1500GI.debug.txt (pastebin works, but if you do email it to the list, please use gzip first)
If the debug log looks like it ended on its own (messages to the effect of not being able to find the device), you may need to wait longer after stopping the driver, or maybe unplug and re-plug the USB cable on the UPS. (Not usually an issue with APC devices, but you never know.)
2018 Aug 30
0
Wrong battery.date variable value
I'm very sorry for the delay here, I've been very swamped with work. Here's the relevant information you guys need:
"upsc APC_BR1500GI" output: https://pastebin.com/rH3W0dbz
"upsrw APC_BR1500GI" output: https://pastebin.com/tEWv8a3d
"upscmd -l APC_BR1500GI" output: https://pastebin.com/MraRQnEk
"clog /var/log/system.log | grep -i ups" output:
2018 Sep 07
2
WinNUT Client Logs
On Fri, 7 Sep 2018, Ong, Kevin wrote:
> Any comments here?
I am not a WinNUT user, but in general NUT clients do not produce their own log
files. If you want more detail, you have to set the debug options and then look
in your system logs.
Upsmon.conf
MONITOR ups at pfsense 1 <username> <password> slave
...
POWERDOWNFLAG /usr/local/ups/etc/killpower
My
2018 Aug 30
0
Wrong battery.date variable value [APC, usbhid-ups]
I don't think the UPS mfr date is accurate also but I'm not a 100% sure. APC replaced my old BR1500GI unit with a brand new one (the one I have now) back in 2015 and this model was one of the newer models back then. So I'd say 2014 to 2015 is more reasonable for the UPS mfr date.
Sorry, I'm more of a PowerShell guy so I don't know much with Linux commands. I tried removing the
2005 Aug 11
4
smbldap-tools unresovled problem.
Hi All,
I am current working on Samba + LDAP PDC in RHEL-4.
I some problem when doing the smbldap-useradd -w command.
When I have a WinXP box try to join the PDC,
smbldap-useradd -w "%u" will add a workstation account to the LDAP tree
with all POSIX attribute but without all the SambaSAMAccount attribute.
So, the WinXP box can find it's workstation account and wouldn't
2018 Aug 30
0
Wrong battery.date variable value [APC, usbhid-ups]
...ntrol-C upsdrvctl start
and then please post the contents of /tmp/APC_BR1500GI.debug.txt (pastebin works, but if you do email it to the list, please use gzip first)
If the debug log looks like it ended on its own (messages to the effect of not being able to find the device), you may need to wait longer after stopping the driver, or maybe unplug and re-plug the USB cable on the UPS. (Not usually an issue with APC devices, but you never know.)
This email may contain material that is confidential, and proprietary to Ingram Micro, for the sole use of the intended recipient. Any review, reliance or...
2018 Sep 04
0
NUT messes up UPS after mains power is restored
UPDATE:
I think I know what I did wrong. In step 7, I plugged the mains too early causing a power race condition as described by point #51 here<https://networkupstools.org/docs/FAQ.html> . I thought that when APC BR1500GI's display went black (even with the fans still running) it is already in a shutdown state. This was not the case, it waited for a few more seconds until it totally
2005 Oct 03
1
chown on smbfs doesn't work ??
Hi,
I have a Network Storage Device mounted as smbfs. When I transfer data
using rsync, the permission of files transferred changes automatically
to 502.501.
I couldn't even issue a command chown. The error message said that
"changing ownership of `thisfile': Operation not permitted
Can someone please advise me to get around with this problem?
--
Best Regards and Thanks,
Ong,
2018 Sep 03
2
NUT messes up UPS after mains power is restored
Hi Charles,
Ok. I'm testing NUT now with only pfsense running as the master and no slaves. I'm noticing a very strange behavior that totally doesn't make sense to me. So here's what I did (in chronological order):
1. Set override.battery.charge.warning to 55 and override.battery.charge.low to 50.
2. I started with a full charge battery and unplugged the UPS from the mains.
2011 Sep 30
2
strict locking and kernel oplocks in the smb.conf
1) Does "strict locking = no" negate "kernel oplocks = yes" ?
2) What's the difference between the two?
3) What a good way to test if a file got a lock seen from the linux side and the windows side?
4) If a file has a lock, does that mean you can still open the file in linux or in windows, but can't write to it?
Any clarification between the two would be helpful.
2009 Jul 20
0
No subject
at least once a week I receive such an attack coming from a different ip.
I will read the articles. Thanks again to everyone.
Regards,
Rodrigo Lang.
2010/6/29 Kenny Watson <kwatson at geniusgroupltd.com>
> Hi, you can use fail2ban
>
2018 Aug 15
0
Wrong battery.date variable value
Denny,
The first three commands had outputs but the "clog /var/log/system.log | grep -i ups” didn't output any. Did I do anything wrong? This is the output without the grep:
can't allocate llinfo for <Public IP> on igb0
Aug 14 18:14:59 pfSense kernel: arpresolve: can't allocate llinfo for <Public IP> on igb0
Aug 14 18:15:00 pfSense kernel: arpresolve: can't