Conference azur::mcc

> Is it possible to change the location of the history files. It appears that they
> are stored in the users default directory - I am running MCC from the root 
> account and the history files are rapidly filling up the root partition, which
> does not have much free space in it. Table 3-3 in the Ultrix Installation Guide
> does not include a variable to change the location of the History files.

Hi Ian,

This experience is from vms but probably holds true for Ultrix also. The
location of the history file is determined by the DOMAIN characteristics.
When you create the domain you can specify the directory. If no directory
is specified then it defaults to wherever you are when you enter mcc. I had
changed our disks and I basically had to delete and recreate the domain out
of the directory where I wanted the history info to be stored. Then rebuild
the domain members. Hindsight would be to use a logical in vms (path in 
ultrix??). 

cheers,
brad...

Brad,

Is this documented anywhere? page 2-14 in the Director Use manual does not 
discuss the significance of the directory field. Having spent a lot of time
building maps and populating domains I am very reluctant to delete them, just
to change the directory pathname so that I can store my history files elsewhere.

Ian

> Is this documented anywhere? page 2-14 in the Director Use manual does not 
> discuss the significance of the directory field. Having spent a lot of time
> building maps and populating domains I am very reluctant to delete them, just
> to change the directory pathname so that I can store my history files elsewhere.

Ian,

I know what you mean. To be honest it may be documented somewhere but I don't
think I've ever seen it anywhere. Maybe the DOC folks can chime in. This
important little tid bit should be in the HISTORICAL DATA SERVICES USE
manual placed just before it shows you the RECORD command. This would at
least outline the significance of domains and their impact on record.

brad...

Is there a way to set the directory under IP auotconfiguration 
or a smiple way to change the diectory of a domain and repopulate it.

I am also reluctant to delete all the doamins I have to move my history
files, but i continually get the following error as I start up the

# /usr/mcc/mmexe/mcc_historian_fm_bg

semget failure: No space left on device



a df indicates a fair amount of space


# df
Filesystem   Total    kbytes   kbytes   %
node         kbytes   used     free     used  Mounted on
/dev/rz2a      19743   14079    3690    79%   /
/dev/rz1g     543710  434643   54696    89%   /usr
/dev/rz0g     271847  132883  111780    54%   /usr/users
/dev/rz0h     271847  184488   60175    75%   /usr/man
/dev/rz2g     205855  170413   14857    92%   /var
#

How much space do I need and where does it need to be in order
to do recording and reporting?

thanks ... scott

># /usr/mcc/mmexe/mcc_historian_fm_bg
>
>semget failure: No space left on device

This is a misleading ULTRIX system message.  It does not refer to disk space.
It is telling you that there are not enough semaphores available on the
system.  I believe that there are directions in the guide for the historian
and exporter that indicate how the relevant system parameters should be set.
Remember to re-build the kernel after changing semaphore parameters
(and copy the new kernel, and reboot).

    
    Hello Scott,
    
    Apparently the message you got, "semget failure: No space left on
    device" does not mean that there is no space for storing historical
    data.  This error appears when Ultrix tries to create a semaphore
    and it cannot create a file in /tmp.  (Sam, thanks for your help!)
    
    Look in /tmp for files with the name "mcc_lock_..."  If you delete
    these files the error you are seeing should disappear.
    
    /tmp is on the / file system, which appears from the results of
    your "df" to have plenty of space.  It is possible that there is
    some ULTRIX system parameter which limits the number of possible
    files in /tmp.  If so, maybe that parameter needs to be changed
    to increase the limit.  Perhaps someone with more ULTRIX system
    management experience could comment here.
                                           
    Where are your Autoconfiguration files stored?  Are they on the
    device where / is mounted?  If not, then moving them will probably
    not help you.  I can tell you how to move them, but first I would
    like to be sure that your effort in moving them will be worthwhile.
    
    Regards,
    
    Ulla
    

    
    One other thing...
    
    The release notes discuss the need to modify system parameters
    and re-configure the kernel to increase shared memory, semaphores
    and max_nofiles.  Have you modified smmax and smseg in
    /sys/conf/mips/HOSTNAME (where HOSTNAME is the name of your system)
    and defined SEMMNI, SEMMNS, SEMMNU and SEMUME as required in
    /sys/h/sem.h and re-configured the kernel?
    
    If not, perhaps doing so would solve your problems with
    semaphores.  See the Release Notes for more information.
    
    Ulla
    
    

1) re. .5 & .7 Thanks for the help on the segment fault error,
I fixed my semaphores and  other parameters and I can record and export fine.

I would still like to know how to move the location of the history files.
See 3) below.

2) Now I have a new problem when I go to run the reports package.  I have set
up recording on IP and TCP under all partitions on a node.  When I run any report
(traffic for IP or TCP) I get the following log file:  Any suggestion? Thanks...

# more tcpip_ip_traffic.rpt.rpt_log

INGRES REPORT -- Copyright (c) 1981, 1990 Ingres Corporation
Reading report specifications and preparing query...
File '/usr/mcc/reports/tcpip_ip_traff_rpt.rw': Start of specifications for Repor
t 'tcpip_ip_traff_rpt'.
E_US0845 Table 'mcc_snmp_ip_13' does not exist or is not owned by you.
    (Thu Sep 10 18:18:17 1992)

E_RW1019 Either you had errors in the .QUERY command, or you didn't
    specify either a .QUERY or .DATA command.  Processing stops.

E_RW100A 1 nonfatal errors have occurred in setting up the report. No
    report will be written.  Correct errors and rerun.
#

3) re: .6 Where are your Autoconfiguration files stored?  - 
If you mean the autotopology
files for the TCP/IP autotopology, I used a directory under /usr

#ls /usr/users/mcc_work/IP/ip/
./                              mcc_ip.dbdump
../                             mcc_ip.edges
mcc_16-67-128-0-hosts.mcc_map   mcc_ip.exceptions
mcc_16-67-224-0-hosts.mcc_map   mcc_ip.mcc_map
mcc_16-67-32-0-hosts.mcc_map    mcc_ip_copy_maps.sh*
mcc_ip.cf                       mcc_ip_deregistration.com
mcc_ip.cfA                      mcc_ip_map.log
mcc_ip.cfB                      mcc_ip_registration.com
mcc_ip.cfC                      mcc_ip_registration.log

I have my map and history files under /

# ls /*mcc*
/mcc_16-67-128-0-hosts.mcc_map
/mcc_16-67-224-0-hosts.mcc_map
/mcc_16-67-32-0-hosts.mcc_map
/mcc_9280000400aa00003a2a92f8e981cb01.mcc_hist_attr012_1
/mcc_9280000400aa00003a2a92f8e981cb01.mcc_hist_attr012_1.dir
/mcc_9280000400aa00003a2a92f8e981cb01.mcc_hist_attr012_p
/mcc_9280000400aa00003a2a92f8e981cb01.mcc_hist_attr012_p.dir
/mcc_9280000400aa00003a2a92f8e981cb01.mcc_hist_inst012_1
/mcc_9280000400aa00003a2a92f8e981cb01.mcc_hist_inst012_1.dir
/mcc_9280000400aa00003a2a92f8e981cb01.mcc_hist_inst012_p
/mcc_9280000400aa00003a2a92f8e981cb01.mcc_hist_inst012_p.dir
/mcc_9280000400aa00003a2a92f8e981cb01.mcc_hist_q12_q
/mcc_ip.mcc_map
/mcc_resource.dat
#

I know I have not done this by design, but brute force, but I'm learning.
If it is not a lot of trouble, I would like to know how to move the 
history files to a different location and/or rerun autopology with a new
domain directory...

thanks ... scott

	Scott,

	I can tell you how to move Autoconfiguration files, but
	know nothing about moving history files.  (Sam, is it
	possible to move these files?)  Read this whole note,
	however, because moving these files may not help you
	achieve your goal of cleaning up the root directory /.
	(If that is your goal.)

	Autoconfiguration uses a "base directory" as a basis
	for creating the IP and DNA4 subdirectories, and subdirectories
	for each domain under IP and DNA4 (IP for IP Autoconfiguration,
	DNA4 for DECnet Phase IV Autoconfiguration).

	You have used "/usr/users/mcc_work" as your base directory.
	Autoconfiguration created /usr/users/mcc_work/IP/ip,
	as the working directory, a place to create map, registration
	files, etc.  In order to move these files you would
	need to choose a new base directory, create the directory
	IP/ip there, and move all the files in /usr/users/mcc_work/IP/ip
	to <new base directory>/IP/ip.  You would need to do the
	same for every directory in /usr/users/mcc_work/IP.

	Then, when you run Autoconfiguration and it asks you 
	to verify your base directory (it assues the current directory
	as a base), type N and enter in the full pathname of your new
	base directory.

	With all that said, if you are trying to clean up the

	If you are running from root and have not defined the
	environment variable MCC_MAPS, DECmcc will look for all
	map files and mcc_resource.dat in / (and Autoconfiguration
	will copy map files from the working directory to / unless
	you tell it not to).  There may be a similar environment
	variable to specify the location of history files, but I do
	not know what it is.

	Hope this helps.

	Ulla