APPLIES TO: Oracle HTTP Server - Version 9.0.2 to 10.1.3.0.0 [Release 9iAS to AS10gR3] Oracle Solaris on SPARC (64-bit) Oracle Solaris on SPARC (32-bit) Web Cache - Version: 9.0.2 to 10.1.3 Solaris Operating System (SPARC 64-bit)Solaris Operating System (SPARC 32-bit) SYMPTOMS: Made one configuration change, adding functionality to listen on port 80. ERROR in error_log after attempting to start: [crit] (13) Permission Denied: make_sock: could not bind to port 80' CHANGES: Operating System was upgraded from Solaris 8 to Solaris 9. Could not start Oracle HTTP Server after upgrade. Ran re-linking instructions, still would not start. CAUSE: In Solaris 9, this option my have been set by default, and the the "nosuid" flag can be set on the Oracle file system mount in vfstab. When that is taken off, and the file system re-mounted, everything should work normally on port 80. Note: This problem can occur with any process, any HTTP Server, where its required to start on a privledged port (1024 or below), where the Solaris 9 is the Operating System in use. SOLUTION: Verify that the file system is not mounted nosuid: % mount /xxx on /xxx/xxx nosuid/read/write If the filesytem is mounted "nosuid", as seen in this example, you will need to unmount the filesystem and mount it without the "nosuid" option. Consult your operating system documentation or your operating system vendor for instruction on modifying mount options. Also check the files: /etc/vfstab /etc/fstab If this is the case then you need to disable the nosuid from the mount points.
Recent Posts