Cisco Unity Connection cannot accept new messages,

[Ahmed Zakariaa]

  Cisco Unity Connection cannot accept new messages, and you may not be able to upgrade Connection.

[Roger Kallberg]

What is your actual question? IMHO The message is quite clear, the storage where you have your messages is full and you'd need to clear up space on it.

[Ahmed Zakariaa]

realy i deleted all messages and still have the issue .

Cisco Unity Connection cannot accept new messages, and you may not be able to upgrade Connection. The location where messages are stored has reached the maximum capacity specified on the Disk Capacity page. You can still send broadcast messages. Instruct Connection users to immediately delete unneeded voice message, and wait up to 30 minutes for the CleanDeleteMessages task to remove deleted messages from the hard disk.

[Nithin Eluvathingal]

It’s possible you only deleted  the messages which move the messages to the Deleted Items folder rather than permanently removing them. Modify the Message Aging Policy to ensure messages in the Deleted folder are permanently deleted, by default it set for 15 days.

Alternatively, you can use the Bulk User Delete option to clear user's mailboxes, which will also free up the space.

https://www.ciscounitytools.com/Applications/CxN/BulkUserDelete/Help/ConnectionBulkUserDelete.htm

2.12.0.0

[Brad Magnani]

As both @Roger Kallberg and @Nithin Eluvathingal mentioned, you'll need to examine your disk usage more closely.  Ensure you have a message aging policy created that is purging messages at regular intervals, and applied to users via their assigned Class of Service.  The first place you'll want to check is under Connection Administration>Message Storage>Mailbox Stores.  There you'll find your mailbox stores, I would expect you'll see yours over quota.  You could temporarily increase the "Maximum Size Before Warning" but if you don't manage the system with aging policies, you'll just fill that new space up and be in the same situation.

If you need to manually run the tasks you can force them from CLI below.  Otherwise, you can schedule and run them from the GUI under Connection Administration>Tools>Task Management.  "Clean Deleted Messages" and "Message Aging" are the ones you'd be looking for.  If you clean each task, you'll also see the task execution history and if there's been any failures to be aware of.

If you force them from CLI, they'll need to be executed on the server running as "Primary" role in the cluster otherwise the command fails with something like:

The value of 'task_name' is not valid or 'task_name' is Singleton
USAGE: run cuc sysagent task task_name
Command failed

run cuc sysagent task Umss.MessageAgingTask (this one assumes you have an existing message aging policy configured and applied to users)
run cuc sysagent task Umss.CleanDeletedMessagesTask

[Ahmed Zakariaa]

After deleting all messages from users inbox as shown below 

Clean Deleted Messages

Message Aging

and still issue

 Cisco Unity Connection cannot accept new messages, and you may not be able to upgrade Connection 

[Nithin Eluvathingal]

I would consider opening a case at this point.

2.12.0.0

[Brad Magnani]

What do the outputs of the following look like?

show status
show cuc dbserver disk

[Ahmed Zakariaa]

admin:show status

Host Name : bpo-unity-pubv12
Date : Thu Mar 27, 2025 11:05:07
Time Zone : Eastern European Time (Africa/Cairo)
Locale : en_US.UTF-8
Product Ver : 12.5.1.10000-23
Unified OS Version : 7.0.0.0-4

Uptime:
11:05:09 up 9 min, 1 user, load average: 0.88, 2.56, 1.61

CPU Idle: 00.00% System: 14.47% User: 05.07%
IOWAIT: 00.00% IRQ: 00.00% Soft: 00.25%

Memory Total: 7992312K
Free: 1739460K
Used: 3327896K
Cached: 3463204K
Shared: 805220K
Buffers: 2924956K

Total Free Used
Disk/active 29223828K 19539432K 9369784K (33%)
Disk/inactive 29223828K 27671180K 45116K (1%)
Disk/logging 102004728K 22057820K 74742276K (78%)

admin:show cuc dbserver disk

Dbspaces
========
Dbspace Dbspace Size Used Free Percent
Number Name MB MB MB Free
------- ---------------------- ---- ---- ---- -------
1 rootdbs 391 134 256 65
2 cuc_er_sbspace 2750 371 2379 86
3 cuc_er_dbspace 250 35 215 85
4 phys 600 600 0 0
5 rpt 3500 499 3001 85
6 temp2 1000 0 1000 99
7 dyn 2477 309 2168 87
8 mbx 250 27 223 89
9 dir16 700 186 514 73
10 log 640 640 0 0
11 temp 1000 0 1000 99
12 mbx16 1000 36 964 96
13 dir 5477 743 4734 86
14 sadmin 100 17 83 82
15 ciscounity_sbspacetemp 960 65 895 93
16 ciscounity_sbspace 20 1 18 92

Chunks
======
Size Free
Chunk Offset MB MB Path
----- ------ ---- ---- ---------------------------------------------------
1 0 391 256 /var/opt/cisco/connection/db/root_dbspace
2 0 2750 2379 /var/opt/cisco/connection/db/cuc_er_sbspace
3 0 250 215 /var/opt/cisco/connection/db/cuc_er_dbspace
4 0 600 0 /var/opt/cisco/connection/db/phys_dbs
5 0 3500 3001 /var/opt/cisco/connection/db/rpt_dbs
6 0 1000 1000 /var/opt/cisco/connection/db/temp2_dbs
7 0 2477 2168 /var/opt/cisco/connection/db/dyn_dbs
8 0 250 223 /usr/local/cm/db/informix/data/mbx_dbs
9 0 700 514 /var/opt/cisco/connection/db/dir16_dbs
10 0 640 0 /var/opt/cisco/connection/db/log_dbs
11 0 1000 1000 /var/opt/cisco/connection/db/temp_dbs
12 0 1000 964 /usr/local/cm/db/informix/data/mbx16_dbs
13 0 5477 4734 /var/opt/cisco/connection/db/dir_dbs
14 0 100 83 /var/opt/cisco/connection/db/sadmin_dbs
15 0 960 895 /var/opt/cisco/connection/db/ciscounity_sbspacetemp
16 0 20 18 /var/opt/cisco/connection/db/ciscounity_sbspace

[Ahmed Zakariaa]

[Andrew Skelly]

What is your Disk Capacity value set to?  By default it is 95%, but did somebody change it to something lower?

System settings - Advanced - Disk Capacity

[Ahmed Zakariaa]

it's already 95%

[Brad Magnani]

The CLI outputs look ok.  As @Andrew Skelly mentioned, what does the Message Storage>Mailbox Stores page look like?  Then if you click on your individual mailbox store(s), what does that look like?

[Brad Magnani]

I did notice in your "show status" output however, your system is running at 100% CPU load since CPU Idle is 0%.

CPU Idle: 00.00% System: 14.47% User: 05.07%

You many also want to run show process using-most cpu and see if it gives any clues.  Otherwise, I would suggest opening a TAC SR to figure out what's going on with your server.