There are multiple way of restarting different aspects of ParaDocs. Please go down this list in order. Only do the last few methods if you ABSOLUTELY have to.
give unix command here and options if OS wont respondIf you have physical access to the machine, you can simple press the power button on the front of the server rack.
If you do NOT have physical access, you can power cycle the machine via the iBoot mechanism.
The Para-Docs DBMS now runs on PostGres, an open-source DBMS http://www.postgresql.com
Two useful (and sometimes required) tools for PostGres:
??
ParaDocs’ profile limits is a method of masking the document profile fields. This means that when a user attempts to enter data into the specified field, the profile field limit/mask will determine which characters and how many characters will actually be taken.
Maybe you want telephone numbers to have dashes in between, Social Security numbers to have 9 digits, or dates to be in dd/mm/yyyy format. You can encourage better data input with the above types of masks.
See the ParaDocs Administrator Documentation for an overview and how to get to the limits editing screen. For details not in that documentation, see below
The syntax derives from a Microsoft VB library called MSMask32.ocx . Lookup the library on Microsofts Developer network or general masking in VB help, for many additional syntaxes.
top ; shows running processes; press 'c' while it is running to see process details; press 'q' to quit screen ; lets you share screens with other people nano ; text editor that lets you use modern keyboard keys psql <database name> ; connect to postgres database in postgres command prompt /sbin/service postgresql restart ; restart the postgres server /sbin/service httpd restart ; restart the http/web server (ussually apache) ps axo pid,tty,stat,bsdstart,bsdtime,command ; list processes with time started and cpu time taken ;postfix any command with '&' to have it run in the background
ps ax ; shows the currently running processes ps ax | grep nps ; returns all currently running processes with the string 'nps' in it. See if one with a reference to 'umbc' in its name is running nano /etc/inittab ; opens a text editor for the inittab file. The [[inittab|http://www.netadmintools.com/html/inittab.man.html]] file describes which processes are started at bootup and during normal operation . Make sure that the line references the posting daemons are not commented out with a # cd /var/paradocs/nps-1.0/ ; changes your current directory ls ; lists the files and directories in the current directory php nps_umbc_import.php ; executes the file nps_umbc_import.php . it goes into a endless loop; end it by hitting ctrl+C pwd ; print working directory. Shows you which dir you are currently in /sbin/telinit Q ; reestablish all inittab settings and processes ps ax ; look for the umbc referencing process in the resultant list \rm -r myDirectory ; remove the directory 'myDirectory' recursively and with no prompts
psql paradocs
Welcome to psql 8.0.6, the PostgreSQL interactive terminal.
Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit
paradocs=# select * from docuser where username = 'story1';
DaySpring provides a complete offsite data backup service. It backs up data (database and pdf repository) nightly and costs us per gigagbyte.
DaySpring is developing a white paper on security and an application to check on status, for the parasync service. Ask about it after December 2006.
The paradocs scheduler / cron process called the ‘paradocs archiver’, is what runs this each night. See Scheduler / Archiver.
Below are shell commands that can be used to assure that parasync backup is running.
[support@gsdocs ~]$ ps ax | grep php ;this command shows all running processes that are php executions 2431 ? Ss 24:54 /usr/bin/php /var/paradocs/nps-1.0/nps_daemon.php 2432 ? Ss 0:01 /usr/bin/php /var/paradocs/nps-1.0/nps_batchscan_daemon.php 2436 ? Ss 1:24 /usr/bin/php /var/paradocs/nps-1.0/nps_autoprofile_daemon.php 2438 ? Ss 0:56 /usr/bin/php -q /var/paradocs/nps-1.0/nps_fileop_daemon.php 2440 ? Ss 0:38 /usr/bin/php /var/www/html/paradocs-4.1/archive_daemon.php 2443 ? Ss 0:01 /usr/bin/php -q /var/paradocs/nps-1.0/nps_file_daemon.php 2449 ? Ss 0:01 /usr/bin/php -q /var/paradocs/nps-1.0/nps_psv_daemon.php 19619 ? Ss 0:00 /usr/bin/php -q /var/paradocs/nps-1.0/nps_umbc_import.php 5031 ? Ss 0:24 /usr/bin/php -q /var/paradocs/nps-1.0/nps_com_daemon.php 6052 pts/0 S+ 0:00 grep php ; look above for archive_daemon.php , this is what runs the parasync nightly; make sure it is always running or backup will not occur [support@gsdocs ~]$ cd /usr/local/data/repository ; move current directorly to repository directory [support@gsdocs repository]$ ls *.dmp ; list all files ending in dmp paradocsdb-1148691602.dmp paradocsdb-1148950822.dmp paradocsdb-1149210026.dmp paradocsdb-1149469225.dmp paradocsdb-1148778029.dmp paradocsdb-1149037214.dmp paradocsdb-1149296403.dmp paradocsdb-1149555611.dmp paradocsdb-1148864421.dmp paradocsdb-1149123641.dmp paradocsdb-1149382852.dmp ; the above shows nightly database dump files. the entire database is contained in each file. each file is backed up via parasync nightly. 14 days are kept.
ParaDocs has a psuedo cron processor that they call the archiver. A database hold specifications for when to run what processes. It is very flexible to do whatever you want whenever.
Scheduled runs are specified in a table in the database. See below for an example:
| table name | archive_schedule |
|---|---|
| attribute name | friendly_name |
| instance | ‘Para-Sync’ |
Located at /var/www/html/paradocs-4.1/pas/