Opened 12 years ago

Closed 7 years ago

#230 closed defect (fixed)

IZ1495: SGE daemons don't start at boot due to install problem on Java Desktop System

Reported by: dom Owned by:
Priority: highest Milestone:
Component: sge Version: 5.3p5
Severity: minor Keywords: Linux install
Cc:

Description

[Imported from gridengine issuezilla http://gridengine.sunsource.net/issues/show_bug.cgi?id=1495]

        Issue #:      1495             Platform:     All      Reporter: dom (dom)
       Component:     gridengine          OS:        Linux
     Subcomponent:    install          Version:      5.3p5       CC:    None defined
        Status:       NEW              Priority:     P4
      Resolution:                     Issue type:    DEFECT
                                   Target milestone: ---
      Assigned to:    andy (andy)
      QA Contact:     dom
          URL:
       * Summary:     SGE daemons don't start at boot due to install problem on Java Desktop System
   Status whiteboard:
      Attachments:

     Issue 1495 blocks:
   Votes for issue 1495:


   Opened: Fri Mar 11 13:01:00 -0700 2005 
------------------------


I received an email from a user who tried to
install SGE 5.3p5 on JDS.
When installing SGE startup script, it states that
the following service is
required to install the startup script.



> We can install the startup script that
> Grid Engine is started at machine boot (y/n) [y] >>
>
> cp /home/sgeadmin/53p5/default/common/rcsge
/etc/init.d/rcsge
> /sbin/insserv /etc/init.d/rcsge
> insserv: Service afs has to be enabled for
service rcsge
> insserv: exiting now!
>


How can I add the aforementioned service (afs)?

BTW, the installation was completed successfully
and the SGE cluster is
functional. The only problem is that the startup
script didn't work at the reboot.

====

NOTE: it is filed OS version suse_linux_8.2
because there's no JDS entry in the OS version.

Suggested Fix:

hansup,

I already noticed that on a different machine with
a newer Suse
distribution.. It looks that the insserv binary
has changed. "afs" is
usually not available on systems and in the past
this caused no problems.

The "afs" requirement is already removed from the
6.0 startup scripts. It
can be safely deleted from the 5.3 start script
template
(util/startup_template) as well.

so the line

   # Required-Start: $network afs

can be changed to

   # Required-Start: $network

Change History (1)

comment:1 Changed 7 years ago by dlove

  • Priority set to highest
  • Resolution set to fixed
  • Severity set to minor
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.