Forum Discussion

akhimik77's avatar
akhimik77
Level 2
22 days ago

Image Cleanup - error 2027

 

Hello! At the moment, we periodically receive a massive error - (2027) The media server is not active.
Image Cleanup performs correctly in the vast majority of tasks.
Job Type - Image Cleanup

......
Apr 26, 2025 6:13:10 AM - Info nbdelete (pid=9992) deleting expired images. Media Server: media4003 Media: @aaaeE
Apr 26, 2025 6:13:10 AM - Error nbdelete (pid=9992) Cannot obtain resources for this job : error [2027]
Apr 26, 2025 6:13:10 AM - requesting resource  @aaaeE
Apr 26, 2025 6:13:10 AM - Error nbjm (pid=8046) NBU status: 2027, EMM status: Media server is not active
Apr 26, 2025 6:13:10 AM - Error nbjm (pid=8046) NBU status: 2027, EMM status: Media server is not active
Media server is not active  (2027)
..............
Apr 26, 2025 2:12:31 AM - Info nbdelete (pid=10762) deleting expired images. Media Server: media4003 Media: @aaaeM
Apr 26, 2025 2:12:31 AM - Error nbdelete (pid=10762) Cannot obtain resources for this job : error [2027]
Apr 26, 2025 2:12:31 AM - requesting resource  @aaaeM
Apr 26, 2025 2:12:31 AM - Error nbjm (pid=8046) NBU status: 2027, EMM status: Media server is not active
Apr 26, 2025 2:12:31 AM - Error nbjm (pid=8046) NBU status: 2027, EMM status: Media server is not active
Media server is not active  (2027)
..............


Please tell me what to do, I haven't really found any information on this error, only special cases that don't fit my case.

4 Replies

Sort By
  • davidmoline's avatar
    davidmoline
    Level 6
    21 days ago

    Hi akhimik77​ 

    You need to identify why the media server (media4003) is reporting that it is inactive. In the java GI, under devices media servers, I suspect the media server is showing as offline. Restarting the media server may help (assuming there are no network issues between the master and media server - such as recent firewall changes). 

    Next review this article that provides a command to make the media server active for disk (and/or tape). https://www.veritas.com/content/support/en_US/article.100006171.html

    There may be more involved in fixing this, but without more information it is difficult to provide. The output from "nbemmcmd -listh -verbose" showing all the info for the media server may assist. 

    One issue may be that the disk pool involved has failed which could cause this same issue - if this is the case, then you may need support to provide assistance. What is the disk pool types for the devices @aaaeE & @aaaeM which are attached to media4003? The output from "nbdevquery -listdv -stype <pool type> -U" showing the relevant pools will help (replace <pool type> with PureDisk or AdvancedDisk or whatever as appropriate). 

    Cheers

     

    • akhimik77's avatar
      akhimik77
      Level 2
      21 days ago

      Restarting the media server service did not help.
      Everything is backed up on this server around the clock without pauses. And on the Advanced Disk and on PureDisk and on the tape. The media server is not displayed as offline at all. The media server is always active for the disc and active for the tape.
      The problem occurs for a very short time, it is almost impossible to catch it with any utility.
      The problem is exclusively with imagex cleanup. 
      Can you tell me which logs can be viewed on this media server?
      By the way, very very rarely, media manager errors occur on this media server, 52 (more often) 54 (less often).

      • davidmoline's avatar
        davidmoline
        Level 6
        20 days ago

        Try looking at the spoold and spad logs for a time when the issue occurred. There are multiple logs in each folder (<MSDP Mount>/log/spoold & <MSDP Mount>/log/spad). The spoold.log and storaged.log (in spoold) and spad.log and sched_QueueProcess.log (in spad) are probably good places to start. In general in these logs search for ERR and WARN to narrow down what you are looking at.

        If this is intermittent, it may be quicker to log a case to have support review the logs etc. 

  • akhimik77's avatar
    akhimik77
    Level 2
    22 days ago

    /usr/openv/pdde/pdcr/bin/crcontrol --processqueue
    it helps temporarily, but after about 8-16 hours, the error starts appearing again
    at the same time, puredisk, advanced disk, and tape library are working correctly and backups are not dropping. Approximately 40,000 tasks are completed per day.
    at the same time, after I executed the //usr/openv/pde/pde/bin/cr control --process queue command for the first time, the media server started working very well, and the number of queues for tasks decreased