Status 0 Installation Aborted Solved Assignment

Posted on by Darn

i'm trying to install airwave 8.2.5 in an AWS centos instance using these instructions:

 

http://community.arubanetworks.com/t5/Monitoring-Management-Location/Install-AirWave-8-0-on-RedHat-RHEL/ta-p/215001

 

when kicking off the install, it errors out immediately after setting the system time:

 

Welcome to AMP Installer Phase 2 STEP 1: Configuring Date and Time ------------------------ Date and Time Configuration --------------------- Current Time: Mon Oct 16 21:33:29 UTC 2017 1) Change Date and Time 2) Change Time Zone 0) Finish > 0 Date and Time Configuration finished. STEP 2: Checking for previous AMP installation Previous AMP installation not found. STEP 3: Installing AMP software This will take a few minutes. Press Ctrl-Alt-F9 to see detailed messages. Press Ctrl-Alt-F1 to return to this screen. Error: AMP installation failed with exit status 0.

i can't find an explanation for this exit status.  while searching the forums, this post is the closest i've found:

 

http://community.arubanetworks.com/t5/Wireless-Access/INSTALLING-AMP-IN-VMWARE/td-p/18868

 

however there are no log files created iin /tmp.  is there any documentation on what this error code means and is there a common place that log files are written during an rpm install?

 

thanks,

 

 

 

  • mpdboot_NODE1 (handle_mpd_output 1000): from mpd on NODE1, invalid port info:

mpd_uncaught_except_tb handling:

<type 'exceptions.IndexError'>: list index out of range

Date:   Sep/2015
 
Nastran 2016.0
 
Avoidance:
export I_MPI_CPUINFO=proc

  •  *** USER FATAL MESSAGE 1221 (GALLOC)

     THE PARTITION OF THE SCRATCH DBSET USED FOR DMAP-SCRATCH DATABLOCKS IS FULL.

     USER INFORMATION: THE DMAP SCRATCH PARTITION WILL NOT SPILL INTO THE 300-SCRATCH PARTITION.

     USER ACTION: 1. SET NASTRAN SYSTEM(151)=1, OR

                  2. INCREASE THE NUMBER OF MEMBERS, AND/OR THEIR MAXIMUM SIZE, FOR THE SCRATCH DBSET ON

                     THE "INIT" STATEMENT.

     BIOMSG: ERROR 4276 HAS OCCURRED IN ROUTINE GALLOC, FILE INDEX = 0.

     STATUS = 0

Date:    Sep/2015

Nastran: 2014.1

Correction Possibilities:

  •   Increase the default SCR size with "sscr" e.g. sscr=2000000

  •   Increase the default BUFFSIZE ( which indirectly increases the SCR size e.g.BUFFSIZE=65537

  •   Allow the SCR to overflow to SCR300 e.g. SYSTEM(151)=1

  •     Signal=11


    Date:    Dec/2013
    Nastran: 2011.1 and 2008
    kernel:  3.0.93-0.8.2.5985.0.PTF-default
    OS:      SLES 11.3
    GLIBC:   2.11.3

    Correction:
    lower stacksize from unlimited to 1024*1024. The problem was unable to be reproduced at MSC

  •     CMA: no RDMA devices found

    Date: Dec/2013

    Cause:
    IntelMPI was trying to use InfiniBand.

    Correction:

    export I_MPI_DEVICE=sock

  •     mpdboot_WG29KB5J.eu.company.com (handle_mpd_output 883): Failed to establish a socket connection with wh29kb5j.eu.company.com:48943 : )     

                 mpdboot_WG29KB5J.eu.company.com (handle_mpd_output 900): failed to connect to mpd on wh29kb5j.eu.company.com


    Date:    Oct/2012
    Nastran: 2012.2
    OS:      Linux64

    Correction: Firewall issue:

    /sbin/service iptables stop

  •     MPI Shared Object "/staff/pjs/msc/20122/msc20122/linux64/intel/lib64/libmpi.so" has been loaded.
     

    librdmacm: couldn't read ABI version.
    librdmacm: assuming: 4
    libibverbs: Fatal: couldn't read uverbs ABI version.
    CMA: unable to open /dev/infiniband/rdma_cm


    Date:    Sep/2012
    Nastran: 2012.2
    OS:      Linux64

    Avoidance: Add the following to your DMP submittal:

    mpiimp=intelmpi symbol=I_MPI_FABRICS=shm:tcp


    The issue is that infiniband RPMs were installed, but

    /usr/sbin/ibstatus

    showed Infiniband was down. The environmental variable forces TCP.

  •     *** USER FATAL MESSAGE (pgm: nastran, fn: main)

    jid=SOL111.dat (command line[2])

    This file exists, but is not readable.

    Date:    Jun/201
    Nastran: 2012.1
    OS:      Linux

    Avoidance: Change the NetAPP setting
    we have solved the problem with Netapp support. We have activated the hidden option nfs.ntacl_display_permissive_perms. Here is the description of this option. Please take notice that the option is hidden and not documented in user documentation.
    This option controls the permissions that are displayed to NFS version 3 and NFS version 4 clients on a file/directory that has an NT ACL set. When enabled, the permissions displayed are based on the maximum access granted by the NT ACL to any user. When disabled, the permissions displayed are based on the minimum access granted by NT ACL to any user. The default value for this option is off.

  •     Error while connecting to host, No connection could be made because the target machine actively refused it. (10061)

                 Connect on sock (host=D00341-2.na.company.com, port=8678) failed, exhaused all end points
                 Unable to connect to 'D00341-2.na.company.com:8678',
                 sock error: Error = -1


    Date:    Sep/2011
    Nastran: MD2011.2
    OS:      Windows 7

    Avoidance: Change path to MPIEXEC from IntelMPI to MS CCP

  •       *** USER FATAL MESSAGE 1004 (CLSPFL)                                                                                               
     

          FORTRAN UNIT CLOSE ERROR.                                                                                                      
          USER INFORMATION:                                                                                                              
               IOSTAT =    28, No error (errno=0)                                                                                        
               LOGICAL = LNKSWH                                                                                                          
               FILE = c:/scratch/instest.T5224_34.f02                                                                                    
     *** SYSTEM FATAL MESSAGE 7301 (FMSCLS)
         CANNOT CLOSE FORTRAN UNIT 2 USED FOR FMS.
    *** SYSTEM FATAL MESSAGE 7300 (FMSOPN)
         FORTRAN UNIT 2 USED FOR FMS HAS BEEN CLOSED AND DELETED.


    Date:    Jul/2011
    Nastran: MD2010
    OS:      Windows

    Avoidance: Change protection on C:/scratch
    Note this was hard to find because they could write to c:/scratch, but the software could not close a file on that file system.

  •     DMP task 1: host="r4i3n10.ice.engr.sgi.com" sdir="/nas/oliviers"

    *** USER WARNING MESSAGE (pgm: nastran, fn: init_rmt_command)
        hosts=r4i3n10:r4i3n11:r4i3n12:r4i3n13     (command line[16])
        Unexpected failure of remote execution request.


    Date:    May/2011
    Nastran: MD2010.1.3
    OS:      Linux

    Avoidance: "Hide" the following files:

    cd $MSC_BASE/$MSC_VERSD/$MSC_ARCH
    mv libcrypto.so.0.9.8 HIDE_libcrypto.so.0.9.8
    mv libssl.so.0.9.8    HIDE_libssl.so.0.9.8

  •     *** USER FATAL MESSAGE 1250 (BIOCRT)

         STATUS =           38, FILX =    3, LOGNAME = MASTER  , NSBUF3 =     8192
         FILE = /home/mev167/nastran-scratch/instest.T26075_52.MASTER
         ERROR MESSAGE IS --
         Function not implemented (errno = 38)

    Date:    Apr/2011
    Nastran: MD2010
    OS:      Linux
    Disk:    LUSTRE file system

    Avoidance: Run with SYS207=1 or

    # mount -t lustre  -o localflock 192.168.0.62@o2ib:/lustre /lustre

  •      *** SYSTEM FATAL MESSAGE 3001 (PRESOL)

         THE INPUT DATA BLOCK NAMED KLL      AT POSITION      1 DOES NOT EXIST.

    Date:     Feb/2011
    Nastran: MD2010
    OS:      Linux
    Option:  DMP

    Avoidance: Run with SCR=YES.
 

  •     *** SYSTEM FATAL MESSAGE (pgm: nastran, fn: run_command_stdin)

        Could not allocate 4611686018427387903 bytes for execv argv

    Date:    Aug/2009
    Nastran: 2008
    OS:      SuSE 11

    Error from ARG_MAX being unlimited on SuSE 11 systems. e.g.:

    suse11-vm <82> getconf ARG_MAX
    2097152

    Avoidance: Reset ARG_MAX. Note this error is fixed in MDR4.

    $HOME/.bashrc:
    # to avoid Nastran 2005.5 erro message ( from Stefan Huttner ):
    #   *** SYSTEM FATAL MESSAGE (pgm: nastran, fn: run_command_stdin)
    #   Could not allocate 4611686018427387903 bytes for execv argv
    # set stacksize to 20MB
    ulimit -s 20000
 

  •     do_ypcall: clnt_call: RPC: timed out


    Date:    Dec/2008
    Nastran: 2008 on x8664

    Avoidance: remove "nis" from /etc/nsswitch.conf
 

  •     Host key verification failed.

    mpirun: Warning one more more remote shell commands exited with non-zero status, which may indicate a remote access problem.

    Date: 12/2/2008
    Nastran: 2008 with x8664 with HPMPI w/ SOL 700

    Avoidance: export MPI_REMSH=rsh
 

  •     /nast/md2009t1/linux64/hpmpi/lib/linux_amd64/plugins/default.so:

    undefined symbol: coll_str_to_interconnect

    Date:    11/6/2008
    Nastran: 2009t1
    Details: x8664 with HPMPI

    Avoidance: export MPI_DISABLE_PLUGINS=1
 

  •     /app/msc/msc20051/linux64/libmkl.so: cannot restore segment prot after reloc:


    Date Reported 9/9/2008 running 2005 on Itanium Gentoo (I think)

    Avoidance: Avoid Security Enhanced Linux (SELinux) by issuing

    chcon -c -v -R -u system_u -r object_r -t lib_t /app/msc/msc20051/linux64/
    chcon -t texrel_shlib_t  /app/msc/msc20051/linux64/libmkl*
 

  •     mpdboot_registration4.localdomain (handle_mpd_output 598): from mpd on compute-0-1.local, invalid port info:

    Warning: No xauth data; using fake authentication data for X11 forwarding.

    Date Reported 7/16/2008 running 2008.0 on an intel cluster with Intel/MPI

    Avoidance: Add the following to $HOME/.ssh/config

    ForwardX11 no
 

  •     *** USER WARNING MESSAGE (pgm: nastran, fn: validate_dmp_hosts)

        C-21-30(LAMn1 ): Unable to make MD Nastran remote query:
        /home/kkcarver/V2007R21/md20071/linux8664/nastran -d0x800000 -rN2007.1
        frs=/home/kkcarver/JOBS/xl0tdf.dat drwx=/scratch/kkcarver
        fw=/home/kkcarver/xltdf16_r21.T14022_56 drwx=/home/kkcarver/JOBS


    Date Reported 4/15/2008 running 2007.1 on a cluster

    Avoidance: Correct $MSC_BASE/md20071/linux8664/nastran.ini. It was missing

    rcmd=/opt/msc/bin/mdnast20071
 

  •     [isll22:13993] [0,1,0] ORTE_ERROR_LOG: Error in file runtime/orte_init_stage1.c at line 626

    --------------------------------------------------------------------------
    It looks like orte_init failed for some reason; your parallel process is
    likely to abort.  There are many reasons that a parallel process can
    fail during orte_init; some of which are due to configuration or
    environment problems.  This failure appears to be an internal failure;
    here's some additional information (which may only be relevant to an
    Open MPI developer):

      orte_session_dir failed
      --> Returned value -1 instead of ORTE_SUCCESS


    Date Reported 1/13/08 running 2008 on a RedHat 4 update 4

    Cause is running with "sdir=.". Note that I could not reproduce the error. Avoidance:
        Run with "sdir=/tmp/BLAH".
 

  •     poll: protocol failure in circuit setup


    Date Reported 1/2/08 running 2008 on a RedHat 3 cluster

    Cause is too many little MPI jobs running with RSH. Avoidances:
        Run fewer DMP jobs at a time.
        Run with s.rsh=ssh (ssh allows more processes).
 

  •     *** USER FATAL MESSAGE (pgm: nastran, fn: validate_authorize)


        authorize=1700@172.16.1.145     (command line[2])

        Host "172.16.1.145" is unknown in this network.


    Date Reported 12/07/2007 running 20055 on a cluster

    Another note is that the user could ping the IP address.
    Avoidance:
        Verify DNS is up. nslookup IP needs to work.
        Put the IP address in /etc/hosts and refer to the host.
 

  •     *** USER WARNING MESSAGE (pgm: nastran, fn: init_rmt_command)

        hosts=em64t4     (command line[3])

        Unexpected failure of remote execution request.
    Segmentation fault (core dumped)


    Date Reported 12/08/2006 running 2006 on an x8664

    Avoidance:
        Remove a file with the same name as specified by "hosts". ie if you have "hosts=em64t4" and a file called "em64t4" in the same directory, you will get this error.
        You can also get this error if the hostname is not resolved via NFS, nslookup, reverse NSlookup, or /etc/hosts. Look in /etc/nsswitch as well.
        With RHEL4.3 as the Master and RHEL 4.5 as the slave, I get this error with "s.rsh=ssh". Changing to "s.rsh=rsh" fixed it 6/27/08. Another fix was to clean my known_hosts file. Although the following worked:

            "ssh remote_node ssh Current_node date"

        Nastran was still failing. I ran with -d16 (ie mdnast2008t2 -d16 JOB dmp=2 hosts=node1:node2) to find the error.
 

  •     --- MSC.Software Installation - Platform Not Supported

     Please Note:
     MSC.Nastran 2005.5 is not supported on
     x86_64 Linux systems.

    You can load any of this product's components on this system, but you
    will not be able to run any applications, and you may not be able to
    use any binary data.



    Date Reported 5/15/2006 installing 2005.5 on an x8664

    Avoidance: The client was trying to install a linux64 (Itanium) system on an x8664 system
    Setting MSCDBG to "mscsetup" prior to running "mscsetup" helped with debugging.
 

  •     signal 11


    Date Reported 2/22/2006 running 2005.5 on an Itanium (LP64) with large model

    Avoidance: increase stack size w/ "ulimit -s unlimited" VVPR 1-24262578.
    Another possibility is to modify the file /etc/security/limits.conf
 

  •     signal 11


    Date Reported Jan/2006 running 2005.1 on an Itanium with ACMS

    Avoidance: Add "param,mdopt14,no". VVPR 1-23754614.
 

  •     does not resolve to 127.0.0.1.


    Date Reported 8/18/2005 running 2005.1.0 on an x8664 RedHat 3 system

    Avoidance: remove the node name from /etc/hosts for 127.0.0.1
 

  •     system error(22): __kmp_create_monitor: pthread_create Invalid argument abort: fatal problem


    Date Reported 3/28/2005 running 2005.0.3 w/ SYS107=2 on an IA64 RedHat 3 system

    Avoidance: set environmental variable:

    export LD_ASSUME_KERNEL=2.4.19
 

  •     FATAL ERROR:

    thread:  191920
    routine: tjoin
    reason:  tid_index_lookup
    error:   -999


    Date Reported 2/10/2005 running SYS107=2 on an IA64 SGI ProPack 3 system

    Avoidance: set environmental variable:
    export LD_PRELOAD="/lib/libc.so.6.1 /lib/libpthread-0.10.so /lib/librt.so.1 /lib/libm.so.6.1"
 

  •      Connection refused


    This error may be a result of:
        inetd not running.
        hostname is in /etc/hosts as 127.0.0.2.
        The following line is not activated in /etc/inetd.conf

          shell   stream  tcp     nowait  root    /usr/sbin/tcpd  in.rshd

        rsh is disabled in /etc/xinetd.d/rsh
        Restart xinetd

          /etc/init.d/xinetd restart
 

  •      Permission denied


    This error is usually a result of one of the following:
        User's .rhosts file does not contain all the nodes.
        User's .rhosts file is 664. To fix, chmod 640 .rhosts
 

  •     rcmd: Node_name.localdomain: Success


    This error may occur if an account was not set up on the remote system. Either create an account or set up NIS.
 

  •     lamnodes (kinit): no running daemon


    This error is because LAM/MPI is not running. Please verify LAM/MPI is running with
    tping -c1 N. If LAM/MPI is not running, use recon and lamboot to start the lam daemon.
 

  •     *** USER WARNING MESSAGE (pgm: nastran, fn: validate_dmp_hosts)

        The current working directory, DIRECTORY, is invalid on
        Node_name.localdomain(LAM n1).


    This error is caused because the current directory does not exist on the remote node.

    *** USER WARNING MESSAGE (pgm: nastran, fn: validate_dmp_hosts)
        Node_name.localdomain: No response from MSC.Nastran remote query:
        drwx=/scratch fw=/net/tux/scratch/dmp.T18776_56 drwx=/net/tux/scratch

    This error may be caused by:
        "ksh" is not installed on the remote node.
        MSC_BASE not being defined in MSC_ARCH/bin/nastran.dmp correctly.
        rcmd not being defined in MSC_ARCH/bin/nastran.ini correctly.
 

  •     *** USER INFORMATION MESSAGE (pgm: nastran, fn: validate_dmp_hosts)

       Node_name.localdomain(LAM n1): Unexpected MSC.Nastran remote query response:
       /nast/bin/nast707 -d0 -rN70.7
       frs=/scratch/myjob.dat drwx=/scratch
       fw=/scratch/myjob.T7000_12 drwx=/scratch

    This error is caused when MSC.Nastran was NOT installed correctly on the remote node.
 

  •     (MSC) Invalid license key (inconsistent encryption code for "NASTRAN")


    This error may be caused because the continuation lines in the license file are messed up.
 

  •     FLEXlm error:  -97,380.  System Error: 111 "Connection refused"


    This error may be caused because there is a MSC_BASE/flexlm/linux/msc which needs to be copied to MSC_BASE/flexlm/linux/MSC.
 

  •     *** USER FATAL MESSAGE 3060 (PREFACE)

       SUBROUTINE MODEL    - OPTION NAST NOT IN APPROVED LIST.
       SYSTEM DATE (MM/DD/YY): 05/08/00
       SYSTEM MSCID:  -2080819589 (DECIMAL) 83F9367B (HEXADECIMAL)

    This error is an authorization problem. It is the result of either:
        DMP was NOT an option in the authorization file.
        The authorization file was not accessible to the first node in the hosts list.
        The system date is not correct.
        It may help to run with authinfo=9 on the command line.
        Consider setting MSC_LICENSE_FILE. e.g.:

           export MSC_LICENSE_FILE=1700@msclic-sa1:1700@msclic-sa2:1700@msclic-la1
           

    *** USER FATAL MESSAGE 3060 (PREFACE)
         - AUTHORIZATION ERROR ***
         UNABLE TO OBTAIN LICENSES FOR Nastran Solver
         PLEASE REFER TO THE LOG FILE FOR ADDITIONAL DETAILS

    This error is an authorization problem. It is the result of either:
        DMP was NOT an option in the authorization file.
        The authorization file was not accessible to the first node in the hosts list.
        The system date is not correct.
        It may help to run with authinfo=9 on the command line.
 

  •     *** SYSTEM FATAL MESSAGE 6062 (DBC)

    *** DIOMSG ERROR MESSAGE     6 FROM SUBROUTINE WRTLST
        OVERFLOW OF DICTIONARY PRIMARY INDEX FOR DATA BASE UNIT     1.


    This error is because the dictionary is too small. To correct 1) increase BUFFSIZE, 2) add an ASSIGN statement with RECL and Size ie:
    assign DBC='S.xdb',status=old,unit=40,recl=65536,size=2147483647

    *** SYSTEM WARNING MESSAGE 6066 (DBC)
    *** DBCMSG ERROR MESSAGE   34 FROM SUBROUTINE DBC
        THE DBC MODULE HAS BEEN TERMINATED BECAUSE OF THE ABOVE FATAL DBC ERROR.
        USER INFORMATION: SUBSEQUENT DBC CALLS WILL NOT BE EXECUTED, AND THE DATABASE CONVERSION IS INCOMPLETE.

    This error is because an old xdb file was left. Note that the f04, f06, and log files get a .# appended, the XDB files do not. remove the old XDB file and resubmit the job.
 

  •     *** SYSTEM FATAL MESSAGE (pgm: nastran, fn: run_command_stdin)

        ./cc574.t3.T18894_49.t3 - errno=2, No such file or directory
    mpirun: process terminated before completing MPI_Init()

    This error occurs when MSC.Nastran is not installed correctly.
 

  •     11:50:14  Processing message string 8:

     11:50:14  ***** LAPI_NewFI

    This error occurs when the date on the system does not match that of the server.
 

  •     Other DMP errors include:
  •         Not specifying F2 on the EIGRL card.
  •         Specifying ND on the EIGRL card.

 

  •     ** EMT signal **


    Command terminated by signal 11

    This error occurs on IA64 systems running RedHat 7.1 with an IA32 headnode using iptables. When ipchains was used instead of IPtables, then the error went away.
 

  •      MSC: The desired vendor daemon is down (-97,121)


    This error is caused when the FlexLM license points to "MSC" as the daemon, but the daemon on /opt/msc/flexlm/linux is called "msc".
 

  •     *** USER WARNING MESSAGE (pgm: nastran, fn: init_rmt_command)

        hosts=heaven:virtue     (command line[4])

        Unexpected failure of remote execution request.

    This error may be caused by one of the following:
        when DMP is specified, and the hostname resolution is incorrect. Please fix /etc/hosts.
        On my SuSE9 system I need to restart xinetd:/etc/init.d/xinetd restart.
 

  •     *** SYSTEM FATAL MESSAGE 1001 (DBOPEN)

         ERROR ENCOUNTERED OPENING FILE, ERROR CODE =  6057.
         DATA BASE NUMBER =   1, UNIT =  40, MESSAGE IS --
         This operation failed because another process already holds a read-write
         or read-only lock on this file.
         Process ID 0 is holding a conflicting lock.
 

  •      *** SYSTEM FATAL MESSAGE (RECEIVE)

         ERROR OPENING XDB FILE '/opt/msc/msc2004t2/linux64/dbc.xdb', RETURN CODE =    5
         XDB NAME LENGTH IS INVALID

    or:

    *** SYSTEM FATAL MESSAGE (RECEIVE)
         ERROR OPENING XDB FILE '/opt/msc/msc2005t1/linux64/dbc.xdb', RETURN CODE =    6
         A READ ERROR OCCURED GETTING DATA


    This error occurs "receiva"e is trying to open a file over an NFS network. To avoid this error, add "nolock" to the /etc/fstab file. ie:
    virtue:/opt/msc /opt/msc nfs rw,bg,soft,intr,nolock
 

  •     *** USER FATAL MESSAGE 1250 (OPNPFL)

         STATUS =         6057, FILX =   40, LOGNAME = DBC     , NSBUF3 =4096
         FILE = PRS_P.xdb
     *** USER FATAL MESSAGE 1250 (OPNPFL)
         ERROR MESSAGE IS --
         This operation failed because another process already holds a read-write
         or read-only lock on this file.
         Process ID 8247 is holding a conflicting lock.
     *** SYSTEM WARNING MESSAGE 6066 (DBC)
     *** DBCMSG ERROR MESSAGE   34 FROM SUBROUTINE DBC
         THE DBC MODULE HAS BEEN TERMINATED BECAUSE OF THE ABOVE FATAL DBC ERROR.
         USER INFORMATION: SUBSEQUENT DBC CALLS WILL NOT BE EXECUTED, AND THE DATABASE CONVERSION IS INCOMPLETE.


    Date Reported 8/11/2005
    Avoidance: Remove the Assignment statment
    This error may be caused from using an ASSIGN statement on a DMP run on an NFS mounted disk. Each process is trying to open up the same file for writing.
 

  •     idalloc: dynamic allocation failed - brk: Cannot allocate memory

       requested size: 471859200 words (1843200 kbytes)
       starting address:           0x0a300000 ( 170917888)
       maximum address requested:  0x7ab00080 (2058354816)

    This error occurs when more memory is requested than allowed. If your computer has more memory, then perhaps you need to:
        Modify /etc/lilo.conf by adding a line similar to:

        append="task_unmapped_base=0xB0000000"

        Run "lilo"
        Reboot
    Also, please note that the memory expressed on the command line through the "mem" parameter is the amount of memory for dynamic common. Additional memory is required for the executable and file buffers. Please see the Configurations and Operations Guide       

Categories: 1

0 Replies to “Status 0 Installation Aborted Solved Assignment”

Leave a comment

L'indirizzo email non verrĂ  pubblicato. I campi obbligatori sono contrassegnati *