Post Reply 
 
Thread Rating:
  • 0 Votes - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
BIBO on limbo305
08-10-2021, 12:50 AM
Post: #4
RE: BIBO on limbo305
install sage stuck
Code:
[root@limbo305-3 ~]# decent_init=True /thinker/local/forest/util/utilib/installx sage
/thinker/local/shed/installation/limbo305-tc                                        
Installing /thinker/local/shed/installation/limbo305-tc/sage.tar.gz ...

log shows some files not found
Code:
...
10.36.3.51:3124 (slot 19)
Start to run the program with 72 VPCs.
Program execution completed.
protocol error: filename does not match request
protocol error: filename does not match request
protocol error: filename does not match request
cat: '/home/sage/think/run/results/result-72-sage/stdout-*': No such file or directory
cat: '/home/sage/think/run/results/result-72-sage/stdout-*': No such file or directory
...
=== Begin Sage Service Test Set ===
./sage_service/sage-service-start.sh
cat: /home/sage/sage/run/service.pid: No such file or directory
cat: /home/sage/sage/run/aide.pid: No such file or directory
Sage is stopped.
          lockstep mark /thinker/globe/.think/lockstep//limbo305-3/sage/tested
          lockstep mark /thinker/globe/.think/lockstep//limbo305-3/sage/decent/workdone

sage start reports need to configure first.
Code:
[sage@limbo305-3 ~]$ ./sage/bin/sage start
ERROR: Sage has not been configured. Please run /home/sage/sage/bin/configure at sage_portal first.
[sage@limbo305-3 ~]$
[sage@limbo305-3 correctness]$ /home/sage/sage/bin/configure
  
====== Generating config.pcf ======
    inferred and exported:
      sage_base: /home/sage/sage
      sage_stdout: /home/sage/sage/stdout/sage.out
      sage_debug: 0
      helper_portal: 10.36.1.49
      sage_ipx: /thinker/etc/ips.cfg
      sage_atp_cnt: 60
  generated /home/sage/sage/config.pcf

====== Generating config.node, sage-svc.inc & hosts.ips ======

-- generating config.node & sage-svc.inc by gen_sage_config

10.36.1.49
10.36.2.50
10.36.3.51
    HELPER_CNT: 6
    HEAVEN_CNT: 1
    ATP_CNT: 60
    backup old config.node: /home/sage/sage/config.node.105847
    backup old sage-svc.inc: /home/sage/sage/sage-svc.inc.105847

Generating walkers from /thinker/etc/ips.cfg
New node: 10.36.1.49
New node: 10.36.2.50
New node: 10.36.3.51
Add fillers
10.36.1.49:1
10.36.1.49:51
10.36.1.49:2
10.36.1.49:51
10.36.1.49:3
10.36.1.49:51
10.36.1.49:4
...
10.36.1.49:51
Adding sage_atp_staff_space_cnt (3), sage_atp_staff_space_start (20) & sage_atp_head_space (14) to config.pcf

Arguments (Part 2):
    WALKER_CNT: 3
    FILLER_CNT: -1
    sage_atp_staff_space_start: 20
    sage_atp_staff_space_cnt: 3
    sage_atp_head_space: 14
  
    config.node is generated in /home/sage/sage/config.node successfully.
    The old config.node is backuped in /home/sage/sage/config.node.105847.
    sage-svc.inc is generated in /home/sage/sage/sage-svc.inc successfully.
    The old svc_inc is backuped in /home/sage/sage/sage-svc.inc.105847.

-- generating hosts.ips from config.node

====== Begin to do the original load.sh ======

Parsing config.node
Configuring for 72 containers
  10.36.3.51 slots: 52
  10.36.1.49 slots: 54 55 56 57 58 59 60 52
  10.36.2.50 slots: 52
  10.36.3.51 slots: 53
  10.36.1.49 slots: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
  10.36.2.50 slots: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
  10.36.3.51 slots: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19
  10.36.1.49 slots: 51 50Obtaining config info
Generating config
Sage is going to format the persistent memory of DT after 10 seconds. Please type Ctrl-C if you do not want to do it.

WARNING: Seems the thinker is running. Refused to format the persistent memory.

This may happen because:
  a) Someone else is using the thinker.
  b) Your program fails or you canceled you program by 'Ctrl-C'.

If you are the one who reserve the thinker for the current time range,
or you are sure that the thinker is running your program, you can
kill the thinker by:

$ dt slay

[sage@limbo305-3 correctness]$ dt slay
...
[sage@limbo305-3 correctness]$ /home/sage/sage/bin/configure
,,,
10.36.3.51:3116 (slot 17)
10.36.3.51:3120 (slot 18)
10.36.3.51:3124 (slot 19)
Start to run the program with 72 VPCs.
Program execution completed.
protocol error: filename does not match request
protocol error: filename does not match request
protocol error: filename does not match request
cat: '/home/sage/think/run/results/result-72-sage/stdout-*': No such file or directory
cat: '/home/sage/think/run/results/result-72-sage/stdout-*': No such file or directory

====== configure is done ====== [0810-11:17:45]
[sage@limbo305-3 correctness]$ echo $?
0
[sage@limbo305-3 correctness]$

sage start reports irresponsive
Code:
[sage@limbo305-3 correctness]$ ~/sage/bin/sage start
Sage is irresponsive. Trying to stop it before start it again.
cat: /home/sage/sage/run/aide.pid: No such file or directory
The prior service instance is perhaps 267779
Sage is stopped.

Starting Sage ..............

log shows
Code:
10.36.1.49 "killall wake_sage detect_listen auntie atpd atpa 2> /dev/null":
10.36.2.50 "killall wake_sage detect_listen auntie atpd atpa 2> /dev/null":
10.36.3.51 "killall wake_sage detect_listen auntie atpd atpa 2> /dev/null":


Sage is stopped.
    sage is to run nohup bash -c 'cd /home/sage/sage/bin; ./start_sage 2>&1 | tee -a /home/sage/sage/stdout/sage.out'
stty: 'standard input': Inappropriate ioctl for device
      store sage_service pid 271612
    start_sage: Tue Aug 10 11:21:10 CST 2021: Sage starts
detect_listen.sh: no process found
[Tue Aug 10 11:21:13 CST 2021] status sage 10.36.1.49 7
        sage state:Sage is stopped or irresponsive. vs. started state:Sage is started.
[Tue Aug 10 11:21:20 CST 2021] status sage 10.36.1.49 7
        sage state:Sage is stopped or irresponsive. vs. started state:Sage is started.
Quote this message in a reply
Post Reply 


Messages In This Thread
BIBO on limbo305 - zhihao - 08-08-2021, 12:35 PM
RE: BIBO on limbo305 - zhihao - 08-08-2021, 12:38 PM
RE: BIBO on limbo305 - lingu - 08-13-2021, 09:30 AM
RE: BIBO on limbo305 - zhihao - 08-08-2021, 07:56 PM
RE: BIBO on limbo305 - zhihao - 08-10-2021 12:50 AM
RE: BIBO on limbo305 - lingu - 08-13-2021, 09:37 AM
RE: BIBO on limbo305 - zhihao - 08-13-2021, 11:30 AM
RE: BIBO on limbo305 - lingu - 08-13-2021, 11:33 AM
RE: BIBO on limbo305 - lingu - 08-13-2021, 09:39 AM
RE: BIBO on limbo305 - lingu - 08-13-2021, 11:43 AM
RE: BIBO on limbo305 - zhihao - 08-13-2021, 11:42 AM
RE: BIBO on limbo305 - lingu - 08-13-2021, 01:15 PM
RE: BIBO on limbo305 - zhihao - 08-13-2021, 12:33 PM
RE: BIBO on limbo305 - lingu - 08-13-2021, 06:15 PM
RE: BIBO on limbo305 - zhihao - 08-13-2021, 01:22 PM
RE: BIBO on limbo305 - lingu - 08-13-2021, 03:18 PM
RE: BIBO on limbo305 - zhihao - 08-13-2021, 04:16 PM
RE: BIBO on limbo305 - lingu - 08-13-2021, 04:07 PM
RE: BIBO on limbo305 - lingu - 08-16-2021, 11:19 AM
RE: BIBO on limbo305 - lingu - 08-16-2021, 05:53 PM
RE: BIBO on limbo305 - zhihao - 08-18-2021, 05:38 PM

Forum Jump: