Forum Discussion

Home_224's avatar
Home_224
Level 6
7 years ago

hatrigger:Failed to send trigger for resfault; script doesn't exist

Dear All,

I check the cluster, there is one group offline and faulted .

I do the two step :

hagrp -clear and hagrp -online , but it still faulted 

B Documentum devuaedms11 Y N ONLINE
B Documentum devuaedms12 Y N ONLINE
B Documentum_ENV_B devuaedms11 Y N OFFLINE|FAULTED
B Documentum_ENV_B devuaedms12 Y N OFFLINE|FAULTED

2018/06/11 11:30:08 VCS INFO V-16-1-50010 Group Documentum_ENV_B is online or faulted on system devuaedms11
2018/06/11 11:30:08 VCS INFO V-16-1-10493 Evaluating devuaedms12 as potential target node for group Documentum_ENV_B
2018/06/11 11:30:08 VCS INFO V-16-1-50010 Group Documentum_ENV_B is online or faulted on system devuaedms12
2018/06/11 11:30:08 VCS INFO V-16-6-15004 (devuaedms11) hatrigger:Failed to send trigger for nofailover; script doesn't exist
2018/06/11 11:30:08 VCS INFO V-16-6-15004 (devuaedms12) hatrigger:Failed to send trigger for resfault; script doesn't exist

May I know how can I fix the issue ?

Thanks you very much 

Alfred 

  • Marianne's avatar
    Marianne
    7 years ago

    Home_224

    Hopefully you had a look at the engineA log in the meantime?

    You will notice that the issue is not with triggers.

    These errors have been logged for months: 

    VxVM vxdctl WARNING V-5-1-9668 CmdLog: write failed - No space left on device
    VxVM vxdg WARNING V-5-1-9668 CmdLog: write failed - No space left on device
    VxVM vxdisk WARNING V-5-1-9668 CmdLog: write failed - No space left on device

    Have you tried to investigate?
    Do you have filesystems that are full?

    The latest issue was with a missing disk:

    VxVM vxdg ERROR V-5-1-587 Disk group cf_bms_dg_01: import failed: Disk for disk group not found
    VxVM vxdg WARNING V-5-1-560 Disk cf_bms_dg_0103: Not found, last known location: EMC1_33

    You need to troubleshoot this at OS-level.
    Ensure all disks can be seen by both nodes. 

    • Marianne's avatar
      Marianne
      Level 6
      7 years ago

      Home_224

      Hopefully you had a look at the engineA log in the meantime?

      You will notice that the issue is not with triggers.

      These errors have been logged for months: 

      VxVM vxdctl WARNING V-5-1-9668 CmdLog: write failed - No space left on device
      VxVM vxdg WARNING V-5-1-9668 CmdLog: write failed - No space left on device
      VxVM vxdisk WARNING V-5-1-9668 CmdLog: write failed - No space left on device

      Have you tried to investigate?
      Do you have filesystems that are full?

      The latest issue was with a missing disk:

      VxVM vxdg ERROR V-5-1-587 Disk group cf_bms_dg_01: import failed: Disk for disk group not found
      VxVM vxdg WARNING V-5-1-560 Disk cf_bms_dg_0103: Not found, last known location: EMC1_33

      You need to troubleshoot this at OS-level.
      Ensure all disks can be seen by both nodes. 

      • Home_224's avatar
        Home_224
        Level 6
        7 years ago

        Thank you for all helpful.

         

        I check the powermt the license not work then I add the license key then do the powercf, powercheck, then hastart to see the mount point right now.