UCCX 7 - Change alert threshold for disk space
We record every call into our UCCX 7 platform which makes my backups quite large. This causes an alert every night when the backups run from CRSAdmin stating that the server is running low on disk space and needs at least 40 GB free for B&R to run.
Is there a way to adjust this threshold?
Thanks
Pablo, thanks for the reply! I checked the event viewer on the UCCX servers and they are clean. This is not a Windows alert. This alert is coming from CRSAdministrator and is routed to the email address I have configured in the email subsystem (Appadmin / Subsystems / email.)
The server is not actually getting low on disk space when this alert is generated, it is simply going below the 40 GB free threshold that is built somewhere in the UCCX application. This is what the actual email looks like:
From CRSAdministrator@AUS-SVR-ICD-01
WARNING: CRS server AUS-SVR-ICD-01(172.21.X.X) is running low in free disk space
**DO-NOT-REPLY-TO-THIS-EMAIL**
CRS required that you have at least 43377659904 bytes available in drive C:, otherwise B&R will fail in operating. Please free up some disk space if required.
-Cisco Customer Response Application Administration.
So maybe the solution is remove the email address I have configured in the email subsystem for alerting and set up a syslog server instead for alarms?
Brett
Similar Messages
-
Tempro v2 - changing threshold for disk space alert
Hello,
I have downloaded and installed Tempro v2 on a Satellite A200. It is running fine.
However, tempro has a problem that was present on the version 1.x .
The low disk space alert is set to trigger, way, way too early at 25% disk space left on any partition. On a modern disk this is around 15GB. This is way , way too early to be told of a problem. I have swiched off this alert - which I don't want to do. There seems to be no way (that I can find) to set this alert to trigger at a more sensible value - say 10% disk space left or a given amount of disk space left - say 2GB.
Is there a fix for this or have I missed how to set this value as I don't want to run without knowing I am running low on disk space? Getting this alert at 25% is irritating.
Thanks
CliveHi
I dont think that you could change this value or settings
Tempro sends the notifications about the status of the whole HDD and therefore you have received this message.
Ive got this tool on my notebook too but didnt find any settings which would help to disable the notification about single partitions on the HDD -
Hi All
I have created an alert of WMI event in sql server which send mail if disk space on D drive is less than 10GB
Query :
SELECT * from __InstanceModificationEvent
WITHIN 60
WHERE
TargetInstance ISA 'CIM_LogicalDisk'
AND
TargetInstance.FreeSpace < 10000000000
AND
TargetInstance.DeviceID = 'D:'
when I enable this alert It sends alert for low disk space
but some time it does'nt send alerts. I am not sure when this __InstanceModificationEvent occure
and is there any another way to alert low disk space in my mailboxTake a look on link:
http://blogs.technet.com/b/fort_sql/archive/2012/08/01/alert-on-low-disk-space-including-mount-points.aspx
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/7a750515-8e82-425d-9c97-f37aac8e149a/monitor-disk-space-using-alerts?forum=sqldatabaseengine
--Please click "Propose As Answer"
if a post solves your problem, or "Vote As Helpful" if a post has been useful to you -
The SCE1010 alert "Not enough disk space"
My SCE1010 show the alert "Not enough disk space" in log.
I find old discuss , someone say can delete the file: /tffs0/SYSTEM/PREVDBG.TXT , because the file is too big.
But I don't confirm delete the file will not effect system work fine.
Could everyone help me to solve the problem ?
Thank you very much.
Log shows:
SCE#>show log | i disk
2012-12-25 00:50:44 | WARN | CPU #000 | Not enough disk space.
2012-12-25 00:50:44 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2012-12-26 09:07:57 | WARN | CPU #000 | Not enough disk space.
2012-12-26 09:07:57 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2012-12-27 17:40:09 | WARN | CPU #000 | Not enough disk space.
2012-12-27 17:40:09 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2012-12-29 01:57:20 | WARN | CPU #000 | Not enough disk space.
2012-12-29 01:57:20 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2012-12-30 11:54:34 | WARN | CPU #000 | Not enough disk space.
2012-12-30 11:54:34 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2012-12-31 20:51:49 | WARN | CPU #000 | Not enough disk space.
2012-12-31 20:51:49 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-02 05:19:01 | WARN | CPU #000 | Not enough disk space.
2013-01-02 05:19:01 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-03 13:31:12 | WARN | CPU #000 | Not enough disk space.
2013-01-03 13:31:12 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-05 03:28:45 | WARN | CPU #000 | Not enough disk space.
2013-01-05 03:28:45 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-06 13:21:00 | WARN | CPU #000 | Not enough disk space.
2013-01-06 13:21:00 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-07 21:18:05 | WARN | CPU #000 | Not enough disk space.
2013-01-07 21:18:05 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-09 05:00:04 | WARN | CPU #000 | Not enough disk space.
2013-01-09 05:00:04 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-10 14:52:16 | WARN | CPU #000 | Not enough disk space.
2013-01-10 14:52:16 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-12 03:29:34 | WARN | CPU #000 | Not enough disk space.
2013-01-12 03:29:34 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-13 13:01:44 | WARN | CPU #000 | Not enough disk space.
2013-01-13 13:01:44 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-14 21:28:53 | WARN | CPU #000 | Not enough disk space.
2013-01-14 21:28:53 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-16 05:30:58 | WARN | CPU #000 | Not enough disk space.
2013-01-16 05:30:58 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-17 19:43:29 | WARN | CPU #000 | Not enough disk space.
2013-01-17 19:43:29 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-19 02:45:28 | WARN | CPU #000 | Not enough disk space.
2013-01-19 02:45:28 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-20 13:22:47 | WARN | CPU #000 | Not enough disk space.
2013-01-20 13:22:47 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-21 21:14:55 | WARN | CPU #000 | Not enough disk space.
2013-01-21 21:14:55 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-23 05:22:05 | WARN | CPU #000 | Not enough disk space.
2013-01-23 05:22:05 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-24 19:14:35 | WARN | CPU #000 | Not enough disk space.
2013-01-24 19:14:35 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-26 04:01:48 | WARN | CPU #000 | Not enough disk space.
2013-01-26 04:01:48 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-27 12:53:58 | WARN | CPU #000 | Not enough disk space.
2013-01-27 12:53:58 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-28 20:36:09 | WARN | CPU #000 | Not enough disk space.
2013-01-28 20:36:09 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-30 06:03:35 | WARN | CPU #000 | Not enough disk space.
2013-01-30 06:03:35 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-01-31 18:56:02 | WARN | CPU #000 | Not enough disk space.
2013-01-31 18:56:02 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-02 02:48:06 | WARN | CPU #000 | Not enough disk space.
2013-02-02 02:48:06 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-03 10:55:07 | WARN | CPU #000 | Not enough disk space.
2013-02-03 10:55:07 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-03 11:50:10 | WARN | CPU #000 | Not enough disk space.
2013-02-03 11:50:10 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-04 21:37:16 | WARN | CPU #000 | Not enough disk space.
2013-02-04 21:37:16 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-06 10:44:39 | WARN | CPU #000 | Not enough disk space.
2013-02-06 10:44:39 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-07 18:46:44 | WARN | CPU #000 | Not enough disk space.
2013-02-07 18:46:44 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-09 03:23:55 | WARN | CPU #000 | Not enough disk space.
2013-02-09 03:23:55 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-10 11:36:02 | WARN | CPU #000 | Not enough disk space.
2013-02-10 11:36:02 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-11 19:53:10 | WARN | CPU #000 | Not enough disk space.
2013-02-11 19:53:10 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-13 09:55:40 | WARN | CPU #000 | Not enough disk space.
2013-02-13 09:55:40 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-14 19:57:55 | WARN | CPU #000 | Not enough disk space.
2013-02-14 19:57:55 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-16 04:20:07 | WARN | CPU #000 | Not enough disk space.
2013-02-16 04:20:07 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-17 12:12:19 | WARN | CPU #000 | Not enough disk space.
2013-02-17 12:12:19 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-19 02:09:51 | WARN | CPU #000 | Not enough disk space.
2013-02-19 02:09:51 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-20 09:41:58 | WARN | CPU #000 | Not enough disk space.
2013-02-20 09:41:58 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-21 17:39:08 | WARN | CPU #000 | Not enough disk space.
2013-02-21 17:39:08 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-23 03:21:28 | WARN | CPU #000 | Not enough disk space.
2013-02-23 03:21:28 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-24 11:18:43 | WARN | CPU #000 | Not enough disk space.
2013-02-24 11:18:43 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-26 00:36:10 | WARN | CPU #000 | Not enough disk space.
2013-02-26 00:36:10 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-02-27 08:13:12 | WARN | CPU #000 | Not enough disk space.
2013-02-27 08:13:12 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-03-27 14:51:13 | WARN | CPU #000 | Not enough disk space.
2013-03-27 14:51:13 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-03-28 22:43:19 | WARN | CPU #000 | Not enough disk space.
2013-03-28 22:43:19 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-03-29 22:44:54 | WARN | CPU #000 | Available disk space at '/tffs0' is 31MB which is under 45MB. Some management operations may fail to execute.
2013-03-30 07:00:26 | WARN | CPU #000 | Not enough disk space.
2013-03-30 07:00:26 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-03-31 07:02:00 | WARN | CPU #000 | Available disk space at '/tffs0' is 35MB which is under 45MB. Some management operations may fail to execute.
2013-03-31 21:27:56 | WARN | CPU #000 | Not enough disk space.
2013-03-31 21:27:56 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-02 05:10:02 | WARN | CPU #000 | Not enough disk space.
2013-04-02 05:10:02 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-03 13:57:11 | WARN | CPU #000 | Not enough disk space.
2013-04-03 13:57:11 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-04 21:24:16 | WARN | CPU #000 | Not enough disk space.
2013-04-04 21:24:16 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-05 21:25:51 | WARN | CPU #000 | Available disk space at '/tffs0' is 31MB which is under 45MB. Some management operations may fail to execute.
2013-04-06 11:11:45 | WARN | CPU #000 | Not enough disk space.
2013-04-06 11:11:45 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-07 18:33:53 | WARN | CPU #000 | Not enough disk space.
2013-04-07 18:33:53 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-09 02:46:02 | WARN | CPU #000 | Not enough disk space.
2013-04-09 02:46:02 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-10 02:47:40 | WARN | CPU #000 | Available disk space at '/tffs0' is 29MB which is under 45MB. Some management operations may fail to execute.
2013-04-10 08:08:00 | WARN | CPU #000 | Not enough disk space.
2013-04-10 08:08:00 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-11 08:09:38 | WARN | CPU #000 | Available disk space at '/tffs0' is 32MB which is under 45MB. Some management operations may fail to execute.
2013-04-11 17:35:16 | WARN | CPU #000 | Not enough disk space.
2013-04-11 17:35:16 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-12 17:36:51 | WARN | CPU #000 | Available disk space at '/tffs0' is 34MB which is under 45MB. Some management operations may fail to execute.
2013-04-13 07:12:46 | WARN | CPU #000 | Not enough disk space.
2013-04-13 07:12:46 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-14 07:14:24 | WARN | CPU #000 | Available disk space at '/tffs0' is 31MB which is under 45MB. Some management operations may fail to execute.
2013-04-14 12:54:48 | WARN | CPU #000 | Not enough disk space.
2013-04-14 12:54:48 | WARN | CPU #000 | Available disk space at '/tffs0' is 44MB which is under 45MB. Some management operations may fail to execute.
2013-04-15 12:56:25 | WARN | CPU #000 | Available disk space at '/tffs0' is 30MB which is under 45MB. Some management operations may fail to execute.
SCE#>Dear Minja.
I have the same problem
Can you see my dir -r ?
SCE#dir -r
File list for /tffs0/
512 WED AUG 13 19:01:34 2008 DIAG DIR
512 WED AUG 13 19:04:00 2008 SYSTEM DIR
512 WED AUG 13 19:13:50 2008 APP DIR
512 WED AUG 13 19:13:50 2008 IMAGES DIR
512 TUE NOV 18 08:48:18 2008 ENGAGE DIR
18189911 TUE APR 16 23:08:26 2013 RELEASE_.SLI
2356 TUE JUN 02 17:14:46 2009 SCRIPT.TXT
7 File(s) 18194827 bytes
File list for /tffs0/DIAG
512 WED AUG 13 19:01:34 2008 . DIR
512 WED AUG 13 19:01:34 2008 .. DIR
2 File(s) 1024 bytes
File list for /tffs0/SYSTEM
512 WED AUG 13 19:04:00 2008 . DIR
512 WED AUG 13 19:04:00 2008 .. DIR
25643 FRI MAY 03 12:02:50 2013 BOOTLOG.TX2
512 WED AUG 13 19:12:46 2008 BACKUP DIR
25441 MON FEB 11 21:30:54 2013 BOOTLOG.TX3
39115 TUE MAY 14 01:29:42 2013 CONFIG.TXT
25658 FRI MAY 03 12:34:36 2013 BOOTLOG.TX1
0 MON FEB 11 13:48:44 2013 BSPFAIL.TXT
25647 SAT MAY 11 06:01:36 2013 BOOTLOG.TXT
0 WED OCT 07 10:18:02 2009 USRCONST.TXT
512 THU OCT 09 05:31:36 2008 PREVCONF DIR
512 WED OCT 07 10:23:12 2009 PQIINST DIR
12 File(s) 144064 bytes
File list for /tffs0/SYSTEM/BACKUP
512 WED AUG 13 19:12:46 2008 . DIR
512 WED AUG 13 19:12:46 2008 .. DIR
9151426 MON FEB 11 21:29:48 2013 DBG_LOG.DF1
16310 MON FEB 11 13:48:56 2013 FAIL.DFL
4 File(s) 9168760 bytes
File list for /tffs0/SYSTEM/PREVCONF
512 THU OCT 09 05:31:36 2008 . DIR
512 THU OCT 09 05:31:36 2008 .. DIR
39115 MON MAY 13 16:06:16 2013 CONFIG.TX8
39115 MON MAY 13 16:26:16 2013 CONFIG.TX7
39115 MON MAY 13 17:24:02 2013 CONFIG.TX6
39115 MON MAY 13 17:28:44 2013 CONFIG.TX5
39115 MON MAY 13 17:51:52 2013 CONFIG.TX4
39115 TUE MAY 14 00:56:44 2013 CONFIG.TX3
39115 TUE MAY 14 01:13:00 2013 CONFIG.TX2
39115 TUE MAY 14 01:29:46 2013 CONFIG.TX1
39115 MON MAY 13 15:38:40 2013 CONFIG.TX9
11 File(s) 353059 bytes
File list for /tffs0/SYSTEM/PQIINST
512 WED OCT 07 10:23:12 2009 . DIR
512 WED OCT 07 10:23:12 2009 .. DIR
2 File(s) 1024 bytes
File list for /tffs0/APP
512 WED AUG 13 19:13:50 2008 . DIR
512 WED AUG 13 19:13:50 2008 .. DIR
17184659 MON FEB 11 21:48:58 2013 EN37592.SLI
3 File(s) 17185683 bytes
File list for /tffs0/IMAGES
512 WED AUG 13 19:13:50 2008 . DIR
512 WED AUG 13 19:13:50 2008 .. DIR
113609411 MON FEB 11 21:09:14 2013 SEOS.PKG
3 File(s) 113610435 bytes
File list for /tffs0/ENGAGE
512 TUE NOV 18 08:48:18 2008 . DIR
512 TUE NOV 18 08:48:18 2008 .. DIR
647546 TUE MAY 14 00:55:44 2013 MYENGAG2.PQB
580274 TUE MAY 14 01:28:48 2013 BATCH.SER
3673 TUE MAY 14 01:29:38 2013 TEMP.DSS
647559 TUE MAY 14 01:11:58 2013 MYENGAG1.PQB
647347 TUE MAY 14 01:28:44 2013 MYENGAGE.PQB
647557 MON MAY 13 17:50:54 2013 MYENGAG3.PQB
8 File(s) 3174980 bytes
373579776 total bytes used
20791296 total bytes free -
How can i change alert tone for incoming messages on my ipad, for imessage?
How can i change alert tone for incoming messages on my ipad, for imessage?
Settings>Sounds>Text Tones
-
Workshop 6u1 installation freezes when checking for disk space
Hi!
I've trying to install Workshop 6 update 1 but while installing and the application is checking for disk space it just freezes on me. One important thing, this system had Workshop 4, 6u1 and 6u2 installed. I removed the package for ws4 and untinstalled ws6u1 and ws6u2 from /var/sadm/prod/com.forte....... for each one of the versions.
Do you have any idea what is going on, why it freezes when checking for disk space???
thanks,
JorgeHi,
command: cmd.exe /c D:\oracle e-business suite R12\oracle ebusiness suite\startCD\Disk1\rapidwiz\bin\adchkutl.cmd C:\cygwin C:\msvc
'D:\oracle' is not recognized as an internal or external command,
operable program or batch file.
RW-50011: Error: - System Utilities Availability test has returned an error: 1Please do not use spaces in directory names, spaces are not allowed and it is expected to get such errors because of the spaces.
Host/Domain
command: ping -n 1 windows7-pc
Pinging WINDOWS7-PC [fe80::4c7b:9a58:f4b2:e7c5%12] with 32 bytes of data:Please note that Windows 7 is not certified as a database/application tier node.
Thanks,
Hussein -
SQL AGENT JOB FOR DISK SPACE USAGE ALERT
Hello Experts
what is the best way to set up a disk space usage alert for my sql server 2008r2 databases. i want to get a notification or alert whenever the disk usage is >80%, thank you as usual.Hi
You can use sql server job for same. I am using below procedure configured with sql job running every 15 mins
Example: EXEC [DBA_DiskSpaceMntr]
@mailto = 'team mail',
@CDrivethreshold = 1024,
@OtherDrivethreshold = 10240
CREATE PROCEDURE [dbo].[DBA_DiskSpaceMntr]
@mailto nvarchar(4000),
@CDrivethreshold INT,
@DDrivethreshold INT,
@YDrivethreshold INT,
@OtherDrivethreshold INT
AS
BEGIN
declare @count int;
declare @DiskFreeSpace int;
declare @tempfspace int;
declare @tempdrive char(1);
declare @mailbody nvarchar(4000);
declare @MailSubject nvarchar(1000);
declare @AlertMessage nvarchar(4000);
declare @altflag bit;
declare @sub nvarchar(4000);
declare @cmd nvarchar(4000);
set @count = 0;
SET @mailbody = '';
SET @cmd = '';
set nocount on
IF EXISTS(select * from sys.sysobjects where id = object_id('#driveinfo'))
drop table #driveinfo
create table #driveinfo(id int identity(1,1),drive char(1), fspace int)
insert into #driveinfo EXEC master..xp_fixeddrives
SELECT @DiskFreeSpace = fspace FROM #driveinfo where drive in ('C')
IF @DiskFreeSpace < @CDrivethreshold
Begin
SET @MailSubject = 'Drive C: free space is low on ' + cast(Serverproperty('Machinename') as nVarchar)
SET @mailbody = 'Drive C: on ' + cast(Serverproperty('Machinename') as nVarchar) + ' has only ' + CAST(@DiskFreeSpace AS VARCHAR) + ' MB left. Please free up space on this drive. '
--select * FROM #driveinfo where drive in ('L')
EXEC msdb.dbo.sp_send_dbmail
@profile_name = 'SQLDBA_Support',
@recipients= @mailto,
@subject = @MailSubject,
@body = @mailbody,
--@file_attachments = @logfile,
@body_format = 'HTML'
End
SELECT @DiskFreeSpace = fspace FROM #driveinfo where drive in ('D')
IF @DiskFreeSpace < @DDrivethreshold
Begin
SET @MailSubject = 'Drive D: free space is low on ' + cast(Serverproperty('Machinename') as nVarchar)
SET @mailbody = 'Drive D: on ' + cast(Serverproperty('Machinename') as nVarchar) + ' has only ' + CAST(@DiskFreeSpace AS VARCHAR) + ' MB left. Please free up space on this drive. '
EXEC msdb.dbo.sp_send_dbmail
@profile_name = 'SQLDBA_Support',
@recipients= @mailto,
@subject = @MailSubject,
@body = @mailbody,
--@file_attachments = @logfile,
@body_format = 'HTML'
End
SELECT @DiskFreeSpace = fspace FROM #driveinfo where drive in ('Y')
IF @DiskFreeSpace < @YDrivethreshold
Begin
SET @MailSubject = 'Drive Y: free space is low on ' + cast(Serverproperty('Machinename') as nVarchar)
SET @mailbody = 'Drive Y: on ' + cast(Serverproperty('Machinename') as nVarchar) + ' has only ' + CAST(@DiskFreeSpace AS VARCHAR) + ' MB left. Please free up space on this drive. '
EXEC msdb.dbo.sp_send_dbmail
@profile_name = 'profile_name',
@recipients= @mailto,
@subject = @MailSubject,
@body = @mailbody,
--@file_attachments = @logfile,
@body_format = 'HTML'
End
set @mailbody='';
while (select count(*) from #driveinfo ) >= @count
begin
set @tempfspace = (select fspace from #driveinfo where id = @count and drive not in ('C','Q','D','Y'))
set @tempdrive = (select drive from #driveinfo where id = @count and drive not in ('C','Q','D','Y'))
if @tempfspace < @OtherDrivethreshold
BEGIN
SET @altflag = 1;
SET @mailbody = @mailbody + '<p>Drive ' + CAST(@tempdrive AS NVARCHAR(10)) + ' has ' + CAST(@tempfspace AS NVARCHAR(10)) + ' MB free</br>'
--SET @cmd = 'dir /s /-c ' + @tempdrive + ':\ > ' + @logfile
--EXEC xp_cmdshell @cmd
END
set @count = @count + 1
end
IF (@altflag = 1)
BEGIN
SET @sub = 'Monitor Space on ' + cast(Serverproperty('Machinename') as nVarchar)
set @mailbody = 'The below drives on ' + cast(Serverproperty('Machinename') as nVarchar) + ' have low disk space then threshold limit ' + CAST(@OtherDrivethreshold as VARCHAR(10)) +' Please free up the space in below specified drives <p>' + @mailbody
--print 'Space on ' + @tempdrive + ': is very low: ' + str(@tempfspace)+ 'MB'
EXEC msdb.dbo.sp_send_dbmail
@profile_name = 'Profile name',
@recipients= @mailto,
@subject = @sub,
@body = @mailbody,
--@file_attachments = @logfile,
@body_format = 'HTML'
END
drop table #driveinfo
set nocount off
END
Thanks Saurabh Sinha
http://saurabhsinhainblogs.blogspot.in/
Please click the Mark as answer button and vote as helpful
if this reply solves your problem -
How to change default thresholds for some metrics of all targets.
Hi!
We have a lot of servers which have to work hard.
So, our OEM very often generates messages like these:
"EM Alert: Critical:dbsora90.tsb.kz - CPU Utilization is 99.95%, crossed warning (80) or critical (95) threshold."
"EM Alert: Critical:dbsora94.tsb.kz - Disk Device c8t60A9800043346C384C344A4A63516D6Ad0(ssd4) is 99.7% busy."
"EM Alert: Critical:dbsora94.tsb.kz - CPU Load (Run Queue Length averaged over 5 minutes) is 20.78, crossed warning (10) or critical (20) threshold."
I need to change default tresholds for mentioned metrics but I can't their defenition in SYSMAN.MGMT_*-tables or suitable settings in OEM GUI.
And I have no time to edit treshholds manually for each target. )Modification of Metric Thresholds (as this is what you are referring to), should be done using the Metrics and Policy Settings link (to be found in the Target Home page).
Don't mess around with the SYSMAN tables!
Best thing to do here is to start using Monitoring Templates for this.
Check:
Oracle® Enterprise Manager Concepts
11g Release 11.1.0.1
http://download.oracle.com/docs/cd/E11857_01/em.111/e11982/toc.htm
Regards
Rob
http://oemgc.wordpress.com -
I'm running the latest OS on my iMac, and I do not use anti-virus software. I have deleted all but a few emails from my Trash and compacted all folders. The Alert message, "There is not enough disk space to download new messages. Try deleting old mail, emptying the Trash folder, and compacting your mail folders, and then try again." continues to appear.
the issue can be caused by a lack of physical disk space, a lack of quota in the disk (user account full), file locking and contention (such a an anti virus or backup program trying to access the same space at the same time. Time machine features in some peoples problems) or as the message suggest large Thunderbird files. As you have looked at the Thunderbird issues, perhaps it is time to look t the broader picture.
-
Can't change alert time for all day event
I have an ipad 4, iOS 6.1.3. When. I set up an all day event and I want to be alerted the day before, the time for the alert is 9am and I can't change it. I went into the settings to make sure there wasn't a default set, and there wasn't. Is this just the way it is and I either take it or leave it? Thanks for your help.
You are correct - you can modify whether to receive an alert for an all day event, and, if so, how far in advance. But once you have chosen to receive the alert the day before the event, the 9AM time is not modifiable. I even checked on iCloud and on my Mac, and the same is true there.
(It turns out that other things that cannot be done on iPad, for example, create a repeating event on, say, the third Tuesday of each month, can be done on the Mac or in iCloud and then will function correctly on iPad.)
Anyway, if you would like to provide feedback to Apple, here's how:
Apple Feedback -
How to remove programs for disk space
In order to backup & restore I need to make room on my disk by removing some programs on my Vaio laptop.How do I do this. I try but everytime I click on REMOVE a error message pops up
Hi zoejacotigiz,
Thank you for considering Sony Community!
Kindly click on this link and follow the instructions on how to uninstall the programs. Here is another link for more troubleshooting steps.
Hope these help.
Regards,
Jen
If my post answers your question, please mark it as "Accept as Solution" -
How to handle too many songs for disk space?
I have a limited collection of fongs on my primary hard drive; most of my collection - about 500GB - is kept on network attached storage. When I install iTunes it copies the music files in My Music to its iTunes Media folder. That's OK for the limited size of My Music - I have enough room on the primary hard drive for the copies. But there is no way I can store a copy of all the files on the NAS. So how do I 'catalog' those files, as well as those on my primary hard drive?
OK, I follow this - except that I read elsewhere (in this forum if memory serves me correctly) that one reason to use the option to copy media to iTunes was so that iTunes would not create duplicate entries - which it seems very fond of doing, no matter how many times I delete them.
If this is not the purpose of the Media folder, then what purpose does it have?
Assuming that I elect to stop this copying, what is the recommended way of removing all the files in the media folder: blunt force with Windows Explorer, or is there an implicit/explicit command somewhere in iTunes that I haven't understood?
And is iTunes limited to just the 1 location for 'sources' of music - or is that what the 'add folder to Library' is meant to do? -
Reports for Low disk space alerts in scom 2007
Dear Experts,
Is there any possible to get the Low disk Space alerts reports in SCOM 2007 R2.
1, I need reports for Last week SCOM sent alerts on Low Disk space for the servers list
2, Likewise I need SCOM Low disk space alerts reports for last month.
Can somebody please explain me with the steps and I played much with Reporting pane.
Thanks,
SaravanaHi,
The below code should work to get all servers that have alert of logical disk free space is low in specific period:
get-alert -criteria 'Name = ''Logical Disk Free Space is low'' AND TimeRaised >=''3/24/2014'' AND TimeRaised <= ''4/24/2014''' | select MonitoringObjectDisplayName,MonitoringObjectPath,Name,TimeRaised | sort MonitoringObjectDisplayName
Here is a similar thread for your reference:
how to create a report showing the servers that had the alerts of "Logical Disk Free Space is low" for a specific period?
http://social.technet.microsoft.com/Forums/en-US/50f2c3fb-2dfc-47c6-8c2a-8a2f0149df10/how-to-create-a-report-showing-the-servers-that-had-the-alerts-of-logical-disk-free-space-is-low?forum=operationsmanagerreporting
Regards,
Yan Li
Regards, Yan Li -
Different disk space alarms for development machines vs. production machines
In vCOps 5.8 I used attribute packages to differentiate between production and development machines on alerting and monitoring for disk space alarms. So if a production machine reached 95% utilization on a drive it would generate an alarm. I set this up in an attributed package and assigned it to production machines. I had a different attribute package assigned to development machines that would not create an alarm. So when a production machine exceeded the 95% threshold I would get an email indicating I needed to take action. I also had some different attribute packages assigned to some production machines that have chronically high disk space usage, but never reach the 100% utilization. These wouldn't alarm at the 95% threshold but maybe at the 99% threshold. In vROps I seem to have lost this ability which I'm not thrilled about. It doesn't appear that you can set different monitoring thresholds for different machines. So now after migrating to vROps I get alarms for development machines. Is there anyway to setup different monitoring thresholds for different machines. I know I could just put a development machine into permanent maintenance mode, but that doesn't really help me out with the ability to set different thresholds for production machines.
Hi, rgcda.
> Are you saying that I need to create new symptom definitions that I want to assign to development machines and then enable them in this specific policy in the Override Alert / Symptom Definitions?
When you define a symptom that triggers over 95% of disk space usage, the default threshold value of the symptom will be 95.
But if you want different threshold value of 99% for your development machines group with the same symptom definition,
you don't have to define another duplicated symptom but just override(modify) the threshold value of original symptom to 99 in the policy edit screen.
In other words, single symptom definition can have different threshold values in each policy.
> Also for alert notifications would I have to create a new alert definition and enable it in is this specific policy?
Nope, you do not have to create a new alert in this case.
If a symptom threshold value changes via policy override, alerts which have that symptom will fire at different threshold value accordingly.
> If I would have different symptom definitions for the same object are you saying I have to make the change in the KB you mentioned?
For instance if I want the C drive to be a critical alarm when it reaches 95% on this machine and a critical when it reached 99% on a different machine.
Nope, as you see in the above example, applying different threshold value to each machine can be done regardless of the metric you use is instanced or not.
The KB is about treating a metric that has many instances for a machine and you may need it for disk space usage.
Regards,
Ho-Sung. -
n I use Boot Camp (Assistant) to change the percentage of disk space allocated to each, without damaging existing MAC applications, files, etc.? Thanks in advance.
make sure Windows will also have the room for updates, cache, page, hibernation, and growth with 20% free space; and Mac should also have 20% or more after accounting for growth.
Spend the $19 and save the headaches with CampTune but backup both - CampTune should help with that chore also but also TimeMachne and clone OS X.
Paragon CampTune for Mac
Maybe you are looking for
-
How do I create an update form, in a search.asp page.
I have a search.asp page which when submitted transfers to the results.asp page. In the search I would like to also create an insert statement. The search.asp page has the following. Form: searchForm (Post) Text Field: KeywordSearch List Menu: Catego
-
Dear All, I'm having one problem in my database. I'm having two database one is testdb1 and another is proddb1 running in two different server. I've done the followings- 1. I've created a dblink from testdb1 to proddb1 database using two different sc
-
Incremental Data loading in ASO 7.1
HI, As per the 7.1 essbase dbag "Data values are cleared each time the outline is changed structurally. Therefore, incremental data loads are supported only for outlines that do not change (for example, logistics analysis applications)." That means w
-
Java.lang.ClassCastException in WD Components
Hi evebody, I facing with a very stranger situation in my WD Component. I have two components, A and B. The component B uses some methods of the Component A, but when I invoke these methods I getting the following exception: java.lang.ClassCastExc
-
hi, i upgraded my portal to sp14. i added new jdbc driver at visual composer. i can connect to the db and select information from my table. when i use the method "last()" i get an error message : Sales naming exception [sap NWMSS] [sqlserver jdbc dri